From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 11:13:29 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:29 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 11:13:29 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 13 11:13:29 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:29 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:29 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:29 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0001.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0002.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0003.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0004.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0005.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0006.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0007.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0008.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0009.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0010.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:01:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:01:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0011.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0012.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0013.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 12:00:56 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 16 12:00:56 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 16 12:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 16 12:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 16 12:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0014.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0015.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0016.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0017.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0018.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0019.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0020.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Jan 18 08:04:33 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0021.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:33 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:33 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:33 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Jan 18 12:01:14 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 18 12:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 18 12:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Jan 18 12:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0022.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0023.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:46 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:46 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:46 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0024.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0025.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0026.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 16:03:35 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Jan 19 16:03:35 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 19 16:03:35 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:35 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 19 16:03:35 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Jan 19 16:03:36 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0027.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:36 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:36 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0028.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0029.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0030.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0031.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0032.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0033.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 21 12:01:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 21 12:01:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 21 12:01:12 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0034.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:12 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:12 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0035.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 21 20:00:58 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:58 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 21 20:00:58 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 21 20:00:58 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0036.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:58 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:58 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:58 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0037.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 22 12:01:01 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 22 12:01:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 22 12:01:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 22 12:01:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0038.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 22 16:01:36 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 22 16:01:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 22 16:01:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 22 16:01:36 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0039.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:36 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:36 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0040.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0041.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0042.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:07 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:07 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:07 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 23 16:02:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 23 16:02:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0043.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0044.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 24 08:03:32 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 24 08:03:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 24 08:03:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 24 08:03:32 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0045.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:32 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:32 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0046.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:38 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0047.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0048.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0049.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0050.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0051.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0052.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 08:06:40 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Jan 26 08:06:42 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 26 08:06:42 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:42 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 26 08:06:42 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Jan 26 08:06:42 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0053.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:42 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:42 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:42 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0054.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:03 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 26 16:01:03 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Jan 26 16:01:03 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0055.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:03 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:03 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:03 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0056.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 27 08:07:39 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 27 08:07:39 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:39 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 27 08:07:39 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 27 08:07:39 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0057.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:39 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:39 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:39 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0058.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0059.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0060.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 08:06:18 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 28 08:06:18 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 28 08:06:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 28 08:06:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 28 08:06:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0061.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0062.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0063.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 20:01:05 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Jan 28 20:01:05 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 28 20:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Jan 28 20:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Jan 28 20:01:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0064.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:05 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0065.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0066.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 29 16:01:03 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 29 16:01:03 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0067.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:03 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:03 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:03 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0068.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 08:10:16 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 30 08:10:18 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 30 08:10:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 30 08:10:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 30 08:10:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0069.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0070.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 30 16:04:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 30 16:04:36 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0071.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:36 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:36 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 20:02:33 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Jan 30 20:02:33 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 30 20:02:33 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:33 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Jan 30 20:02:33 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Jan 30 20:02:33 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0072.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:33 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:33 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:33 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 08:08:33 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 31 08:08:33 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 31 08:08:33 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:33 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 31 08:08:33 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 31 08:08:34 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0073.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:34 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:34 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:34 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 12:04:47 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 31 12:04:47 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 31 12:04:47 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:47 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 31 12:04:47 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 31 12:04:47 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0074.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:47 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:47 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:47 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0075.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 20:01:21 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Jan 31 20:01:21 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 31 20:01:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Jan 31 20:01:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Jan 31 20:01:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0076.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0077.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 12:03:04 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 1 12:03:04 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 1 12:03:04 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:04 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 1 12:03:04 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 1 12:03:04 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0078.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:04 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:05 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 1 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 1 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0079.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0080.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 08:14:33 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Feb 2 08:14:34 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 2 08:14:34 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:34 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 2 08:14:34 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Feb 2 08:14:35 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0081.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:35 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:35 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:35 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Feb 2 12:03:15 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 2 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 2 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Feb 2 12:03:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0082.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0083.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 2 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 2 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Feb 2 20:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0084.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 08:13:53 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Feb 3 08:13:54 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 3 08:13:54 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:54 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 3 08:13:54 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Feb 3 08:13:54 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0085.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:54 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:54 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:54 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 12:03:09 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Feb 3 12:03:09 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 3 12:03:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 3 12:03:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Feb 3 12:03:09 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0086.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:09 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:09 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0087.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 20:01:21 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Feb 3 20:01:21 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 3 20:01:22 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:22 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 3 20:01:22 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Feb 3 20:01:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0088.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:22 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 08:09:20 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Feb 4 08:09:21 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 4 08:09:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 4 08:09:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Feb 4 08:09:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0089.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0090.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 16:01:27 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Feb 4 16:01:27 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 4 16:01:27 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:27 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 4 16:01:27 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Feb 4 16:01:27 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0091.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:27 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:27 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:27 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0092.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Feb 5 08:08:21 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 5 08:08:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 5 08:08:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Feb 5 08:08:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0093.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0094.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0095.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0096.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 08:17:01 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Feb 6 08:17:01 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 6 08:17:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 6 08:17:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Feb 6 08:17:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0097.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 12:03:15 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Feb 6 12:03:15 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 6 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 6 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Feb 6 12:03:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0098.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0099.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 20:01:16 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Feb 6 20:01:16 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 6 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 6 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Feb 6 20:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0100.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:16 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:16 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 08:26:58 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Feb 7 08:27:00 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 7 08:27:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:27:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 7 08:27:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Feb 7 08:27:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0101.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:27:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:27:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:27:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0102.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0103.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0104.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:21 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 08:26:04 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 8 08:26:06 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 8 08:26:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:26:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 8 08:26:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 8 08:26:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0105.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:26:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:26:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:26:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 8 12:04:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0106.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:01 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:01 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0107.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 8 20:01:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 8 20:01:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0108.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0109.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Feb 9 12:03:45 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0110.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:45 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:45 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:45 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Feb 9 16:01:32 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 9 16:01:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 9 16:01:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Feb 9 16:01:32 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0111.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:32 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:32 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:32 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0112.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 08:25:15 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Feb 10 08:25:18 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 10 08:25:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:25:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 10 08:25:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Feb 10 08:25:19 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0113.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:25:19 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:25:20 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:25:20 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 12:04:06 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Feb 10 12:04:06 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 10 12:04:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 10 12:04:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Feb 10 12:04:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0114.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:06 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:06 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0115.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0116.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 08:13:55 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Feb 11 08:13:55 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 11 08:13:55 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 11 08:13:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Feb 11 08:13:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0117.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0118.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Feb 11 16:01:18 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 11 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 11 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Feb 11 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0119.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:18 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:18 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0120.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:11 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 08:10:36 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Feb 12 08:10:37 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 12 08:10:37 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:37 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 12 08:10:37 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Feb 12 08:10:38 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0121.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:38 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:38 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:38 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Feb 12 12:03:15 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 12 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 12 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Feb 12 12:03:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0122.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:15 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:15 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0123.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0124.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 08:19:06 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Feb 13 08:19:07 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 13 08:19:07 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:19:07 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 13 08:19:07 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Feb 13 08:19:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0125.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:19:10 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:19:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:19:10 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Feb 13 12:03:37 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0126.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:37 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:37 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:37 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Feb 13 16:01:40 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 13 16:01:40 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:40 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 13 16:01:40 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Feb 13 16:01:40 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0127.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:40 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:41 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:41 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0128.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:23 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 08:21:28 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Feb 14 08:21:30 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 14 08:21:30 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:30 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 14 08:21:30 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Feb 14 08:21:31 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0129.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:31 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:31 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:31 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0130.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0131.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0132.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 08:32:56 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 15 08:32:59 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 08:32:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:32:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 08:32:59 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 15 08:33:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0133.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:33:02 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:33:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:33:02 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 15 12:06:09 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0134.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:09 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:09 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:09 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 16:01:50 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:50 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 16:01:50 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 15 16:01:50 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0135.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:50 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:50 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:50 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0136.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 20:15:21 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Wed Feb 15 20:15:21 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 20:15:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Wed Feb 15 20:15:21 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Wed Feb 15 20:15:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0137.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:22 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:22 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 16 08:49:56 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Thu Feb 16 08:49:57 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 16 08:49:57 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:49:57 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Thu Feb 16 08:49:58 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Thu Feb 16 08:50:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0138.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:50:00 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:50:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:50:00 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Tue Apr 5 18:03:00 2005 From: support at egenix.com (Charlie Clark) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] Re: [egenix-sales] Error Message In-Reply-To: References: Message-ID: <20050405170300.49727.31@Zeta.1112688786.fake> On 2005-04-05 at 16:46:32 [+0200], Scott Robinson wrote: > I am evaluating your mxODBC Zope DA Zope product and I am running into the > following error message every once in awhile. I need to reboot the linux box > in order to clear it up. I have tried adding a timeout to the FreeTDS > driver, but that hasn't work. I was wondering if you had any suggestions or > if this was either a problem with FreeTDS or possibly unixODBC. > > Error Type: ProgrammingError > Error Value: ('07005', 20019, '[unixODBC][FreeTDS][SQL Server]Attempt to > initiate a new SQL Server operation with results pending.', 1023) Dear Scott, as FreeTDS is still in development we cannot recommend it and cannot really provide support for its use in connection with mxODBC. We would suggest you try another ODBC bridge such as that provided by Easysoft to see if the error still occurs. Sincerely Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From support at egenix.com Mon Apr 25 10:54:50 2005 From: support at egenix.com (eGenix Support) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] Re: [egenix-info] mxODBC In-Reply-To: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> References: <000801c547b4$2a7e1ac0$6501a8c0@CompaqXP> Message-ID: <20050425095450.1845.1@bepc.1114415307.fake> On 2005-04-23 at 05:25:58 [+0200], K. Schreur wrote: > Sir/Madam: > I have installed the mxODBC Windows package and I am attempting to > understand how it works. I have tried to perform a simple connection to a > database, and while it appears the connections works properly, when I try > to execute a simple SQL statement I receive the following: > > Traceback (most recent call last): > File "C:/Python24/kstest", line 4, in -toplevel- > c.execute('select count(*) from RetailAccounts') > AttributeError: 'builtin_function_or_method' object has no attribute > 'execute' > >>> > > I believe this to be some sort of installation issue on my part, but I do > not know where to find out how to resolve it. Could someone please assist? > I believe it to be a very simple issue that I don't understand. > Regards, > Kevin Schreur Dear Mr Schreur, without more from your script it is very difficult to say anything about your error except that it probably has little to do with mxODBC because the error you are getting specifies a Python builtin. To help you more we need the complete script. Regards Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Tue Apr 26 15:39:32 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? Message-ID: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The Python interpreter was configured with a command similar to: OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... --without-pymalloc mx base 2.0.6, built with this Python interpreter, segfaulted when I tried to use it; I didn't try to pursue that issue. mx base 2.1.0b5 works fairly well, but causes the Python interpreter to fail a reference counting integrity check and abort when bogus arguments are passed to mx.DateTime.DateTime. Example: ------------------------------------------------------------ py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" Fatal Python error: UNREF invalid object Aborted ------------------------------------------------------------ I have no familiarity with the mx code base, but from looking at mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that function 'mxDateTime_Free' is registered as the destructor for type 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by 'mxDateTime_Deallocate', which is called by 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is then called again by the Python garbage collector (even though the object in question has already been subjected to 'PyObject_Del()' by the previous execution of 'mxDateTime_Free'). In other words: ------------------------------------------------------------ mxDateTime_FromDateAndTime(erroneous args) -> mxDateTime_Deallocate(datetime) -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) ... [Python garbage collector] -> mxDateTime_Free(datetime) -> PyObject_Del(datetime) /* aborts */ ------------------------------------------------------------ Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Deallocate' in the 'onError' handler, or 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mal at egenix.com Wed Apr 27 11:33:27 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> References: <20050426213933.33779.qmail@web30015.mail.mud.yahoo.com> Message-ID: <426F4E57.1080809@egenix.com> David Rushby wrote: > I'm using a heavy-debug build of Python 2.4.1 on i386 Linux. The > Python interpreter was configured with a command similar to: > OPT="-DPy_DEBUG -DCOUNT_ALLOCS" ./configure --prefix=... > --without-pymalloc > > mx base 2.0.6, built with this Python interpreter, segfaulted when I > tried to use it; I didn't try to pursue that issue. This is a known bug in 2.0 and fixed in 2.1.0b5. We don't use Python debug builds and the problem only appears in those special Python builds - not in the regular ones. > mx base 2.1.0b5 works fairly well, but causes the Python interpreter to > fail a reference counting integrity check and abort when bogus > arguments are passed to mx.DateTime.DateTime. Example: > ------------------------------------------------------------ > py24d -c "import mx.DateTime as dt; dt.DateTime(-1, 13, 32)" > Fatal Python error: UNREF invalid object > Aborted > ------------------------------------------------------------ > I have no familiarity with the mx code base, but from looking at > mx/DateTime/mxDateTime/mxDateTime.c, the problem appears to be that > function 'mxDateTime_Free' is registered as the destructor for type > 'mxDateTime_Type', but 'mxDateTime_Free' is called explicitly by > 'mxDateTime_Deallocate', which is called by > 'mxDateTime_FromDateAndTime' in case of error, and 'mxDateTime_Free' is > then called again by the Python garbage collector (even though the > object in question has already been subjected to 'PyObject_Del()' by > the previous execution of 'mxDateTime_Free'). > > In other words: > ------------------------------------------------------------ > mxDateTime_FromDateAndTime(erroneous args) > -> mxDateTime_Deallocate(datetime) > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) > ... > [Python garbage collector] > -> mxDateTime_Free(datetime) > -> PyObject_Del(datetime) /* aborts */ > ------------------------------------------------------------ > > Perhaps 'mxDateTime_FromDateAndTime' should call 'Py_DECREF(datetime)' > instead of 'mxDateTime_Deallocate' in the 'onError' handler, or > 'mxDateTime_Deallocate' should call 'Py_DECREF(datetime)' instead of 'mxDateTime_Free(datetime)'? Nice analysis. Are you using the standard mxDateTime build or one with WANT_SUBCLASSABLE_TYPES defined (mxDateTime_Deallocate is only used by the latter) ? In any case, please try our latest snapshot: http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip to see if that makes any difference. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From davidrushby at yahoo.com Wed Apr 27 07:09:06 2005 From: davidrushby at yahoo.com (David Rushby) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: 6667 Message-ID: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> --- "M.-A. Lemburg" wrote: > Are you using the standard mxDateTime build or one > with WANT_SUBCLASSABLE_TYPES defined... Presumably "the standard", since I just built with 'py24d setup.py build', making no attempt to enable special directives. > ... (mxDateTime_Deallocate is only used by the latter)? That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > In any case, please try our latest snapshot: > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > > to see if that makes any difference. I can't build it out of the box: --- # py24d setup.py build Traceback (most recent call last): File "setup.py", line 9, in ? import mxBASE File "/usr/src/egenix-mx-base-2.1.0-20050415/mxBASE.py", line 10, in ? from mxSetup import mx_Extension ImportError: No module named mxSetup --- If I copy mxSetup.py from 2.1.0b5 to 2.1.0-20050415, then the C compiler can't find mx.h: mx/DateTime/mxDateTime/mxDateTime.c:41:16: mx.h: No such file or directory Transferring all of the mx.h files from 2.1.0b5 to 2.1.0-20050415 seems a sure way to generate a corrupt build, so I stopped there. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From TJones at OptioSoftware.com Fri Apr 29 12:06:25 2005 From: TJones at OptioSoftware.com (Tim Jones) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Message-ID: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> -----Original Message----- From: Tim Jones Sent: Friday, April 29, 2005 10:58 AM To: egenix-users@lists.egenix.com Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Tim Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050429/61f390e2/attachment-0139.htm From mal at egenix.com Fri Apr 29 18:59:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] mx base 2.1.0b5 ref count bug? In-Reply-To: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> References: <20050427130906.52878.qmail@web30008.mail.mud.yahoo.com> Message-ID: <427259F3.4090806@egenix.com> David Rushby wrote: > --- "M.-A. Lemburg" wrote: > >>Are you using the standard mxDateTime build or one >>with WANT_SUBCLASSABLE_TYPES defined... > > > Presumably "the standard", since I just built with 'py24d setup.py > build', making no attempt to enable special directives. > > >>... (mxDateTime_Deallocate is only used by the latter)? > > > That's true in 2.1.0-2005-04-15, but not in 2.1.0b5. > > >>In any case, please try our latest snapshot: >> >> > > http://www.egenix.com/files/python/egenix-mx-base-2.1.0-2005-04-15.zip > >>to see if that makes any difference. > > > I can't build it out of the box: Hmm, looks like distutils' sdist command doesn't like our new repository layout which uses symlinks (after we've switched to subversion). We'll have to debug distutils first, I guess :-( -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 19:01:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A62@mail.optiosoftware.com> Message-ID: <42725A67.5000206@egenix.com> Tim Jones wrote: > > -----Original Message----- > From: Tim Jones > Sent: Friday, April 29, 2005 10:58 AM > To: egenix-users@lists.egenix.com > Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") > > > > Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 Can you provide some context with your problem report. What have I suggested and where ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Fri Apr 29 21:44:43 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") In-Reply-To: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> References: <9F61F758A669B34A93BA1A4179F8CE62537A64@mail.optiosoftware.com> Message-ID: <4272809B.5070106@egenix.com> Tim Jones wrote: > sorry I thought I was replying to the message. Anyways the subject of the message is the same with date being Tue Aug 17 10:43:36 2004 started by Robby Dermody. Specifically you mentioned taking the ; out of the DSN string after PWD and checking the odbc.ini file. Like Rob said I can use isql, tsql, and iodbctest fine but the mx unixODBC or iODBC does not seem to work properly with FreeTDS. I haven't heard of any reports in either direction. Looking at the old posting (appended below) and the version numbers mentioned in it, I'd suggest that you simply upgrade to the latest versions of all components. FreeTDS has seen a lot of development since 0.61, egenix-mx-commercial is now at version 2.0.7 and the other components have also had a lot of development since August 2004. > thanks > Tim Jones > > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Friday, April 29, 2005 12:02 PM > To: Tim Jones > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] MS SQL ODBC connect problem ("Option not > supported") > > > Tim Jones wrote: > >> >>-----Original Message----- >>From: Tim Jones >>Sent: Friday, April 29, 2005 10:58 AM >>To: egenix-users@lists.egenix.com >>Subject: [egenix-users] MS SQL ODBC connect problem ("Option not supported") >> >> >> >>Has anybody solved problem. The things suggested by Marc-Andre do not work. I have the exact same setup on Redhat Linux and it works fine ... it just does not work on AIX 5.1 > > > Can you provide some context with your problem report. What have > I suggested and where ? > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 29 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Robby Dermody wrote: > >> Hi guys, >> >> This problem has been causing me to pull my hair out for the last day or >> two. I'm trying to use mxODBC under Debian Linux 'unstable' to connect >> to a MS SQL database via either unixODBC or iODBC. >> >> Relevant versions: >> mxODBC: 2.0.6 >> mx-base: 2.0.5 >> unixodbc: 2.2.4-9 >> iodbc: 3.51.2 >> freetds: 0.61 >> >> With both unixODBC and iODBC, I have installed them, configured >> odbc.ini, and can use their test programs to connect to this database >> and query it fine. No problems there. However, when I mix mxODBC into >> the picture and try to connect via that, I get something like the >> following: >> >> >>>>> db = >> >> >> mx.ODBC.unixODBC.DriverConnect("DSN=testdsn;UID=testuser;PWD=pass;") >> Traceback (most recent call last): >> File "", line 1, in ? >> mxODBC.NotSupportedError: ('S1C00', 1, '[unixODBC]Option not supported', >> 5921) >> >> >> Here's the mxodbc.log output (when compiled in 'debug' mode): >> >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=1 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 mxODBC_New_UseDriverConnect: failed. >> mxODBC_New_UseDriverConnect: dsn='DSN=testdsn;UID=testuser;PWD=pass;', >> clearAC=0 >> mxODBC_ReportError: sqlstate='S1C00' code=1 text='[unixODBC]Option not >> supported' lineno=5921 rc=-1 >> mxODBC_New_UseDriverConnect: failed. >> >> >> I get the same output from iodbc, "Option not supported". Any idea how >> to find out WHAT option they're talking about? Note I get the same error >> when using Connect(), and as you can see, I've tried it with both clear_auto_commit=1 and clear_auto_commit=0 ...same thing each >> time. >> >> I'm thinking this is a problem between mxODBC and unixodbc/iodbc....and >> that it has nothing to do with freeTDS or the MS SQL server itself. > > > mxODBC does work with FreeTDS, so the problem must be with your setup. > > Two things: > > 1. try to remove the final ";" in your DSN > > 2. check your odbc.ini file whether you are using unsupported > connection options. > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Aug 17 2004) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::