http://permalink.gmane.org/gmane.comp.python.egenix.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.python.egenix.user/1258 ________________________________________________________________________ ANNOUNCING eGenix.com mxODBC Connect Python Database Interface Version 0.9.3 (beta) Our new client-server product for connecting Python applications to relational databases - from all major platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-mxODBC-Connect-0.9.3-beta.html ________________________________________________________________________ INTRODUCTION The mxODBC Connect Database Interface for Python allows users to easily connect Python applications to all major databases on the market today in a highly portable and convenient way. Unlike our mxODBC Python extension, mxODBC Connect is designed as client-server application, so you no longer need to find production quality ODBC drivers for all the platforms you target with your Python application. Instead you use an easy to inst eGenix Team: M.-A. Lemburg 2008-11-12T15:38:37 http://permalink.gmane.org/gmane.comp.python.egenix.user/1257 FYI: We've upgraded to SP4 (8.00.2039) now, but still can't recreate the problem. M.-A. Lemburg 2008-11-06T14:53:50 http://permalink.gmane.org/gmane.comp.python.egenix.user/1256 Hmm, looks like we're missing some service pack on ours. But then: your version should have fewer bugs - at least in theory. We have added a similar test to our test suite and ran the test several times. All passed and no crashes. I've also had a look at the ODBC log and all I could find is the same problem that you find in the crashing ones: the cursor state is always invalid after you call the procedure. I can't tell from here, but this looks a lot like a problem in the ODBC driver or your setup. We can't reproduce the problem with our setup and have already invested a fair amount of time into trying to help you with this without being able to really determine a problem in mxODBC. As a result, we have to ask you to get a support ticket(s) to continue working on your problem: http://www.egenix.com/services/support/ We can then provide you with a special debug build of mxODBC and analyze the logs it generates. Thanks, M.-A. Lemburg 2008-11-06T11:22:33 http://permalink.gmane.org/gmane.comp.python.egenix.user/1255 We've added a test similar to what you're doing to out suite, but cannot reproduce the problem: Loaded mx.ODBC.Windows version 3.0.2 Testing package mx.ODBC.Windows version: 3.0.2 compiled with Unicode support using Python version: 2.5 Test suite: Connecting to the database. Connected to DSN DSN: sqlserver; Database: master; Server: PICASSO; User: dbo; DBMS: Microsoft SQL Server; Version: 08.00.0760; ODBC driver: SQLSRV32.DLL 03.85.1132; ODBC Version: 03.52 String encoding used by mxODBC: utf-8 StoredProcedureTest: executing create table mxODBC0001 (col1 int, col2 int) StoredProcedureTest: executing CREATE PROCEDURE sp_mxODBC0001 AS DECLARE < at >var1 int, < at >var2 int DECLARE cursor1 CURSOR FOR SELECT col1, col2 FROM mxODBC0001 ORDER BY col1 OPEN cursor1 FETCH NEXT FROM cursor1 INTO < at >var1, < at >var2 WHILE < at >< at >FETCH_STATUS = 0 BEGIN SELECT < at >var1 AS col1, < at >var2 AS col2 M.-A. Lemburg 2008-11-05T16:25:08 http://permalink.gmane.org/gmane.comp.python.egenix.user/1254 No that's not possible without patching mxODBC. The ODBC manager will normally translate between the application and the driver, however, it only does this if the driver itself advertises itself as being a 2.0 driver. We'll setup a few new tests to try to reproduce the problem. Thanks. M.-A. Lemburg 2008-11-05T15:04:08 http://permalink.gmane.org/gmane.comp.python.egenix.user/1253 M.-A. Lemburg ha scritto: Very interesting... It is possible to force mxODBC to use only the ODBC 2.0 API? There are newer drivers for SQL Server 2000? Of course, you will find it in the attachment. Thank you for your help. Sirio Capizzi 2008-11-05T14:55:49 http://permalink.gmane.org/gmane.comp.python.egenix.user/1252 mxODBC 3.0 tries to use the ODBC 3.x API where possible, so that may explain why you are seeing different behavior compared to mxODBC 2.0. The SQL Server 2000 ODBC driver is rather old, so it's possible that it doesn't support the ODBC 3.x API all that well. However, our tests pass just fine for that driver as well, but AFAIK we don't use cursors in the tested stored procedures, so that's something to add to the test suite. Could you send us an ODBC trace that shows the crash (ie. stops after the crash) ? M.-A. Lemburg 2008-11-05T14:12:41 http://permalink.gmane.org/gmane.comp.python.egenix.user/1251 M.-A. Lemburg ha scritto: Yes, I have tried it on the server side and it works correctly. Moreover on the same client was installed mxODBC 2.0.6 for python 2.3 and it worked fine too. After upgrading to python 2.5 and mxODBC 3.0.2 we got this problem but only on stored procedures using cursors (the others work fine). So I think that this behavior is caused by the new mxODBC library. You are right. However the connectionoption doesn't influence the behavior of the callproc function. In fact without this line python still crashes. Sirio Capizzi 2008-11-05T13:52:28 http://permalink.gmane.org/gmane.comp.python.egenix.user/1250 Have you tried this in the SQL Server Management GUI ? Since the stored procedure runs entirely on the server side, I don't think that mxODBC or the ODBC driver can cause this behavior. The segfault is likely caused by the above option setting: SQL.CURSOR_TYPE is a *cursor* option, not a connection option, so you're adjusting some unknown option on the connection to some unknown value. BTW: Please don't change the SQL.CURSOR_TYPE value - mxODBC uses static cursors for efficiency and also to enable scrolling in result sets. M.-A. Lemburg 2008-11-05T13:04:59 http://permalink.gmane.org/gmane.comp.python.egenix.user/1249 Yes, the if clause is intended and the problem doesn't depend on it. The problem is that each time you execute the stored procedure you got a different numer of rows even if the procedure uses the same set of data. The python script we are using is the following: import mx.ODBC.Windows from mx.ODBC.Windows import SQL conn=mx.ODBC.Windows.Connect('db3','user','password') conn.setconnectoption(SQL.CURSOR_TYPE,SQL.CURSOR_DYNAMIC) cur = conn.cursor() cur.callproc('CursorTest') cur.close() conn.commit() The version of the SQL Server ODBC driver is 2000.85.1132.00 Sirio Capizzi 2008-11-05T11:45:53 http://permalink.gmane.org/gmane.comp.python.egenix.user/1248 See below - there's an IF clause there that applies filtering. Could you send us the Python script (or snippet) you used to trigger the segfault ? Segfaults in mxODBC itself are rare - segfaults in the underlying ODBC driver unfortunately not, but we always try to add work-arounds for these buggy drivers if possible, so feedback is appreciated. The above IF will likely filter out a few rows. Is that intended ? Thanks, M.-A. Lemburg 2008-11-05T10:54:09 http://permalink.gmane.org/gmane.comp.python.egenix.user/1247 Hi all, we have a problem using egenix mxODBC with a stored procedure using cursors. The scenario is the following: a Windows XP based client tries to call a stored procedure on a Microsoft SQL Server 2000 using python 2.5 and mxODBC 3.0.2. The procedure simply copies all the rows of a table to another one using cursors. The call succeeds but a random numer of rows are copied instead of the full table. We have tried with execute, executedirect and callproc. Execute and executedirect complete but only a random number of rows are copied. Callproc crashes and a windows error report dialog pops up saying that an error occured in mxodbc.pyd. We also tried .setconnectoption(SQL.CURSOR_TYPE,SQL.CURSOR_DYNAMIC) but with no results. Someone can help us? Thank you in advance. The stored procedure looks like the following, attaced you will find the odbc connection trace: USE [db3] GO /****** Oggetto: StoredProcedure [user].[CursorTest] Data script: 11/05/2008 08:44:39 ******/ SET ANSI_NULLS ON GO SET Sirio Capizzi 2008-11-05T08:50:50 http://permalink.gmane.org/gmane.comp.python.egenix.user/1246 What's in those src/mx folders ? Note that you should not put the mx package itself on sys.path, but instead its parent path. You could start python using the -vv flag. It will then print all the locations it search for modules and packages. M.-A. Lemburg 2008-10-24T09:13:08 http://permalink.gmane.org/gmane.comp.python.egenix.user/1245 When following the above advice I am unable to get my instance to start. When trying to start the instance I get: "ImportError: cannot import name TextTools" /usr/lib/python2.4/site-packages/mx Instead of the src/mx folder in my buildout. Any ideas? Here is my [zopepy] section from buildout.cfg: [zopepy] recipe = zc.recipe.egg eggs = ${instance:eggs} interpreter = zopepy extra-paths = ${zope2:location}/lib/python ${buildout:directory}/src/mx src/mx scripts = zopepy Is there a better way to get mxODBCZopeDA working with buildout? Is there more information I should include to make this easier to troubleshoot? Thanks for any advice. Israel _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users Israel Carr 2008-10-21T14:53:53 http://permalink.gmane.org/gmane.comp.python.egenix.user/1244 ________________________________________________________________________ ANNOUNCING eGenix.com mx Base Distribution Version 3.1.1 for Python 2.6 Open Source Python extensions providing important and useful services for Python programmers. This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-mx-Base-Distribution-3.1.1-for-Python-2.6.html ________________________________________________________________________ ABOUT The eGenix.com mx Base Distribution for Python is a collection of professional quality software tools which enhance Python's usability in many important areas such as fast text searching, date/time processing and high speed data types. The tools have a proven record of being portable across many Unix and Windows platforms. You can write applications which use the tools on Windows and then run them on Unix platforms without change due to the consistent platform inde eGenix Team: M.-A. Lemburg 2008-10-15T15:41:09 http://permalink.gmane.org/gmane.comp.python.egenix.user/1243 ________________________________________________________________________ ANNOUNCING eGenix.com mxODBC - ODBC Database Interface for Python Version 3.0.2 mxODBC is our commercially supported Python extension providing ODBC database connectivity to Python applications on Windows and Unix platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-mxODBC-3.0.2-GA.html ________________________________________________________________________ INTRODUCTION mxODBC provides an easy-to-use, high-performance, reliable and robust Python interface to ODBC compatible databases such as MS SQL Server, MS Access, Oracle Database, IBM DB2 and Informix , Sybase ASE and Sybase Anywhere, MySQL, PostgreSQL, SAP MaxDB and many more. The "eGenix mxODBC - ODBC Database Interface for Python" product is a commercial extension to our open-source eGenix mx Base Distribution. * About Python: Python is eGenix Team: M.-A. Lemburg 2008-10-15T15:41:57 http://permalink.gmane.org/gmane.comp.python.egenix.user/1242 ________________________________________________________________________ ANNOUNCING eGenix.com mxODBC Connect Database Interface for Python Version 0.9.2 (beta) Our new client-server product for connecting Python applications to relational databases - from all major platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-mxODBC-Connect-0.9.2-beta.html ________________________________________________________________________ INTRODUCTION The mxODBC Connect Database Interface for Python allows users to easily connect Python applications to all major databases on the market today in a highly portable and convenient way. Unlike our mxODBC Python extension, mxODBC Connect is designed as client-server application, so you no longer need to find production quality ODBC drivers for all the platforms you target with your Python application. Instead you use an easy to in eGenix Team: M.-A. Lemburg 2008-10-01T17:49:41 http://permalink.gmane.org/gmane.comp.python.egenix.user/1241 Dear Users, due to a problem with the upload to our server, the distribution files were not accessible. The problem has now been corrected. M.-A. Lemburg 2008-09-25T17:38:09 http://permalink.gmane.org/gmane.comp.python.egenix.user/1240 ________________________________________________________________________ ANNOUNCING eGenix.com pyOpenSSL Distribution Version 0.7.0-0.9.8i-1 An easy to install and use repackaged distribution of the pyOpenSSL Python interface for OpenSSL - available on Windows and Unix platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-pyOpenSSL-Distribution-0.7.0-0.9.8i-1-GA.html ________________________________________________________________________ INTRODUCTION The eGenix.com pyOpenSSL Distribution includes everything you need to get started with SSL in Python. It comes with an easy to use installer that includes the most recent OpenSSL library versions in pre-compiled form. pyOpenSSL is an open-source Python add-on (http://pyopenssl.sf.net/) that allows writing SSL aware networking applications as well as certificate management tools. OpenSSL is an eGenix Team: M.-A. Lemburg 2008-09-25T13:57:12 http://permalink.gmane.org/gmane.comp.python.egenix.user/1239 mxODBC cannot load the unixODBC manager shared libraries. You will either have to add the path to these to your system configuration file ld.so.conf or setup LD_LIBRARY_PATH to include them. Regards, M.-A. Lemburg 2008-09-22T09:37:14 http://permalink.gmane.org/gmane.comp.python.egenix.user/1238 _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users kw_dev_lists-maGkBM8SPcwgA6DENJS+mtBPR1lH4CV8< at >public.gmane.org 2008-09-19T18:02:47 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.python.egenix.user