http://blog.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/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 install Python client library which connects directly to the mxODBC Connect database server over the network. This makes mxODBC Connect the ideal basis for writing cross-platform database programs and utilities in Python, especially if you run applications that need to communicate with databases such as MS SQL Server, Oracle or DB2 that run on Windows or Linux machines. By removing the need to install and configure ODBC drivers on the client side, mxODBC Connect greatly simplifies setup and configuration of database driven client applications, while at the same time making the network communication between client and database server more efficient and more secure. For more information, please have a look at the product page: http://www.egenix.com/products/python/mxODBCConnect/ * About Python: Python is an object-oriented Open Source programming language which runs on all modern platforms (http://www.python.org/). By integrating ease-of-use, clarity in coding, enterprise application connectivity and rapid application design, Python establishes an ideal programming platform for todays IT challenges. * About eGenix: eGenix is a consulting and software product company focused on providing professional quality services and products to Python users and developers (http://www.egenix.com/). ________________________________________________________________________ NEWS mxODBC Connect 0.9.2 is our second public beta release of the new mxODBC Connect product. It comes with improved documentation, enhanced SQL Server support on Linux and now runs on Python 2.6 as well (in addition to Python 2.3, 2.4 and 2.5). *SPECIAL OFFER* If you would like to participate in the beta as tester, please see our beta program page: http://www.egenix.com/products/python/mxODBCConnect/beta.html In order to make participation in the beta program more interesting for our users, we will be giving out *free discount coupons* to all participants who report back bugs in the product. ________________________________________________________________________ DOWNLOADS The download archives as well as instructions for installation and configuration of the product can be found on the product page: http://www.egenix.com/products/python/mxODBCConnect/ _______________________________________________________________________ SUPPORT Commercial support for this product is available from eGenix.com. Please see http://www.egenix.com/services/support/ for details about our support offerings. Enjoy, 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 open-source implementation of the SSL protocol (http://www.openssl.org/). * About Python: Python is an object-oriented Open Source programming language which runs on all modern platforms (http://www.python.org/). By integrating ease-of-use, clarity in coding, enterprise application connectivity and rapid application design, Python establishes an ideal programming platform for todays IT challenges. * About eGenix: eGenix is a consulting and software product company focused on providing professional quality services and products to Python users and developers (http://www.egenix.com/). ________________________________________________________________________ NEWS This second release of the eGenix.com pyOpenSSL Distribution upgrades the included OpenSSL library version to the latest 0.9.8i, which includes several bug fixes over the previously included 0.9.8h version. The release also includes Python 2.6 support for the first time. Binaries are available for Linux x86 and x64 as well as Windows x86. ________________________________________________________________________ DOWNLOADS The download archives and instructions for installing the package can be found at: http://www.egenix.com/products/python/pyOpenSSL/ ________________________________________________________________________ UPGRADING Before installing this version of pyOpenSSL, please make sure that you uninstall any previously installed pyOpenSSL version. Otherwise, you could end up not using the included OpenSSL libs. _______________________________________________________________________ SUPPORT Commercial support for these packages is available from eGenix.com. Please see http://www.egenix.com/services/support/ for details about our support offerings. Enjoy, 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 http://permalink.gmane.org/gmane.comp.python.egenix.user/1237 Am 18.09.2008, 23:37 Uhr, schrieb <kw_dev_lists-maGkBM8SPcwgA6DENJS+mtBPR1lH4CV8< at >public.gmane.org>: No, that isn't necessary. The usual problem with data sources, drivers and the like is making sure that the permissions are correct, ie. so that the Zope user can access them. When testing on the command line you will normally be using your own user account. Charlie Charlie Clark 2008-09-19T12:52:40 http://permalink.gmane.org/gmane.comp.python.egenix.user/1236 _______________________________________________________________________ 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-18T21:37:43 http://permalink.gmane.org/gmane.comp.python.egenix.user/1235 Oops. Sorry, that was a quote form our support wiki. MS tends to change their site structure very often. Ok. M.-A. Lemburg 2008-09-18T16:15:40 http://permalink.gmane.org/gmane.comp.python.egenix.user/1234 _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users Brad Allen 2008-09-16T23:30:01 http://permalink.gmane.org/gmane.comp.python.egenix.user/1233 Without more details about the used database backend, server and client platforms as well as ODBC driver, there's nothing much we can do to help. Some drivers allow tweaking the way pre-fetching and network packet sizes are handled, thus reducing the number of network round-trips. You might also want to check whether mxODBC Connect is faster for your setup: http://www.egenix.com/products/python/mxODBCConnect/ M.-A. Lemburg 2008-09-12T20:23:45 http://permalink.gmane.org/gmane.comp.python.egenix.user/1232 Hi, I'm running mxODBC on a machine that remotely connects to the server, and when I'm executing scripts, it takes 20 minutes longer than it would on the server itself. Is there any way to speed up the connection? Thanks, Minh _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users Minh-Long Pham 2008-09-12T19:49:52 http://permalink.gmane.org/gmane.comp.python.egenix.user/1231 This can be done, but is not available for the released product, since we only include interfaces for iODBC and unixODBC. The reason for this is simple: the ODBC standard is a very complex API and the ODBC managers help work around at least some of the issues you find in practice when using ODBC drivers. (For many other quirks we have work-around in mxODBC itself.) We can provide you with custom versions for such a setup (ie. mxODBC directly linked against the FreeTDS driver), but cannot support such setups and also have to charge a support ticket for the extra work. I'd really recommend against using such a setup. It doesn't buy you anything much in terms of performance. If you're looking for better performance, it's better to look at alternative ODBC drivers for talking to MS SQL Server. We will also be releasing a mxODBC Connect Zope DA soon after the final release of mxODBC Connect, our new bridge product for working with ODBC drivers that are installed directly on the database server machine and talk to the database via shared memory and/or pipes. For MS SQL Server, you can then use a Linux client machine and work against the SQL Server Native Client installed on the Windows server. You no longer need an ODBC driver for your client machine and even get better performance due to the optimized setup. M.-A. Lemburg 2008-09-11T21:43:25 http://permalink.gmane.org/gmane.comp.python.egenix.user/1230 _______________________________________________________________________ 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-11T19:21:45 http://permalink.gmane.org/gmane.comp.python.egenix.user/1229 Very strange indeed. You can check the version number by looking at connection.driver_version I get 09.00.3042 for out installation of SQL Server native client. connection.driver_name is 'SQLNCLI.DLL'. Ok, so it's not related to data conversion either. Could you please try to run the query on a fresh new cursor (ie. one that hasn't executed any queries yet) and see whether that makes a difference ? If that doesn't help, the next thing we could try is an ODBC trace. These are the instructions to enable such a trace on Windows: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcsetting_tracing_options.asp If standard tracing doesn't work, you could try the Visual Studio Analyzer: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcenabling_visual_studio_analyzer.asp Note that tracing has to be enabled for the user account that the application is using in MDAC 2.8. There's a new option in MDAC 2.8 which also allows machine wide tracing (which was the only option in MDAC 2.7 and prior versions): http://support.microsoft.com/default.aspx?scid=kb;en-us;818489 Please send us the trace snippet for the query in question. Thanks, M.-A. Lemburg 2008-09-11T17:44:51 http://permalink.gmane.org/gmane.comp.python.egenix.user/1228 M.-A. Lemburg wrote: I those "_3" aliases were created by Storm's ClassAlias; I discovered a parameter that would allow me to specify the name when creating the ClassAlias instances. That got rid of the "_3" aliases in the query, and there are no more quoted identifiers, and now the query is more readable. However, it still fails when using cursor.execute and succeeds when using cursor.executedirect. I was using the normal SQL Server driver; I changed to the SQL Server native client but am still seeing the same behavior. As far as whether it's the latest, it's the version that comes with Windows Server 2003 Standard Edition Service Pack 3. I think Storm is handling that by building a tuple of a tuple of strings, just like we would normally pass to cursor.execute for bind parameters. I haven't checked to see exactly what it is doing there, but we aren't having any issues with parameter substitution for any of our other queries. Brad Allen 2008-09-11T15:28:51 http://permalink.gmane.org/gmane.comp.python.egenix.user/1227 You have 8 '?' markers in your query, so that looks fine. However, the query is rather complicated with respect to all the joins, so it's possible that the ODBC driver doesn't parse the query correctly and perhaps misses out on some of the parameter markers. It may also get confused by the "_3" aliases. Why the quotes and why double-quotes instead of square brackets ?. What setting do you use for QUOTED_IDENTIFIERS ? Some more general questions: Are you using the most recent SQL Server Native client on the Windows machine ? How are you converting the params before using them on cursor.execute() ? M.-A. Lemburg 2008-09-11T10:08:37 http://permalink.gmane.org/gmane.comp.python.egenix.user/1226 The plain .execute() uses a prepare step, SQL type binding and does some processing directly on the client, whereas .executedirect() sends all data to the server for processing and uses Python type binding for parameters. Could also post the query and parameters that caused this problem ? The error is related to a parameter you have in the query which the client apparently does not detect correctly. Thanks. M.-A. Lemburg 2008-09-10T15:23:17 http://permalink.gmane.org/gmane.comp.python.egenix.user/1225 _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users Brad Allen 2008-09-10T13:48:16 http://permalink.gmane.org/gmane.comp.python.egenix.user/1224 Hello Brad, On 2008-09-10 04:18, Brad Allen wrote: No, that's not possible without wrapping the cursor object and then redirecting the method in the wrapper. Note that cursor.execute() will work like cursor.executedirect() when called without parameters. You should check the performance of using one over the other. cursor.executedirect() will bypass the prepare step, so the statement will have to be parsed and processed over and over again. Some database backends do clever caching on the server, so this is not an issue, in fact, it's faster for simple queries since you avoid a few network round-trips. For other backends, it's slower, since they don't implement such caching. Another issue is related to parameter binding: using cursor.executedirect() the ODBC driver does not have any parameter type information available (this only becomes available via the prepare step), so mxODBC cannot do any efficient conversion to database data types on the client side. This may result in conversion problems on the server side and introduce extra overhead. M.-A. Lemburg 2008-09-10T09:13:15 http://permalink.gmane.org/gmane.comp.python.egenix.user/1223 Hello, I am using mxODBC 3 with the Storm ORM, which makes use of cursor.execute. I would like to find a way to configure mxODBC to use executedirect without having to change or override Storm's call to cursor.execute. Is there some way to configure mxODBC to use the executedirect behavior when cursor.execute is called? Thanks. Brad Allen 2008-09-10T02:18:55 http://permalink.gmane.org/gmane.comp.python.egenix.user/1222 Hi, Thanks very much for the snapshot package. Yes indeed that has got me up and running. Mit freundlichen Gruessen, Darryl Cousins _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users Darryl Cousins 2008-09-05T20:31:42 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.python.egenix.user