<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.comp.python.egenix.user">
    <title>gmane.comp.python.egenix.user</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1242"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1241"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1240"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1239"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1238"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1237"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1236"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1235"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1234"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1233"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1232"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1231"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1230"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1229"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1228"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1227"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1226"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1225"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1224"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.egenix.user/1223"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1242">
    <title>ANN: eGenix mxODBC Connect Database Interface for Python 0.9.2 (beta)</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1242</link>
    <description>________________________________________________________________________

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</description>
    <dc:creator>eGenix Team: M.-A. Lemburg</dc:creator>
    <dc:date>2008-10-01T17:49:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1241">
    <title>Re: ANN: eGenix pyOpenSSL Distribution 0.7.0-0.9.8i-1</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1241</link>
    <description>Dear Users,

due to a problem with the upload to our server, the distribution files
were not accessible. The problem has now been corrected.

</description>
    <dc:creator>M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-25T17:38:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1240">
    <title>ANN: eGenix pyOpenSSL Distribution 0.7.0-0.9.8i-1</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1240</link>
    <description>________________________________________________________________________

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 </description>
    <dc:creator>eGenix Team: M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-25T13:57:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1239">
    <title>Re: Getting mxODBCZopeDA connector topick-upenvironment ODBC DNSs</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1239</link>
    <description>
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,
</description>
    <dc:creator>M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-22T09:37:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1238">
    <title>RE: Getting mxODBCZopeDA connector to pick-upenvironment ODBC DNSs</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1238</link>
    <description>
_______________________________________________________________________
eGenix.com User Mailing List                     http://www.egenix.com/
https://www.egenix.com/mailman/listinfo/egenix-users
</description>
    <dc:creator>kw_dev_lists-maGkBM8SPcwgA6DENJS+mtBPR1lH4CV8&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2008-09-19T18:02:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1237">
    <title>Re: Getting mxODBCZopeDA connector to pick-upenvironment ODBC DNSs</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1237</link>
    <description>Am 18.09.2008, 23:37 Uhr, schrieb &lt;kw_dev_lists-maGkBM8SPcwgA6DENJS+mtBPR1lH4CV8&lt; at &gt;public.gmane.org&gt;:


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
</description>
    <dc:creator>Charlie Clark</dc:creator>
    <dc:date>2008-09-19T12:52:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1236">
    <title>Getting mxODBCZopeDA connector to pick-up environment ODBC DNSs</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1236</link>
    <description>
_______________________________________________________________________
eGenix.com User Mailing List                     http://www.egenix.com/
https://www.egenix.com/mailman/listinfo/egenix-users
</description>
    <dc:creator>kw_dev_lists-maGkBM8SPcwgA6DENJS+mtBPR1lH4CV8&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2008-09-18T21:37:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1235">
    <title>Re: cursor.executedirect configurable?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1235</link>
    <description>
Oops. Sorry, that was a quote form our support wiki. MS tends to
change their site structure very often.


Ok.



</description>
    <dc:creator>M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-18T16:15:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1234">
    <title>Re: cursor.executedirect configurable?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1234</link>
    <description>
_______________________________________________________________________
eGenix.com User Mailing List                     http://www.egenix.com/
https://www.egenix.com/mailman/listinfo/egenix-users
</description>
    <dc:creator>Brad Allen</dc:creator>
    <dc:date>2008-09-16T23:30:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1233">
    <title>Re: Speeding up ODBC Connection</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1233</link>
    <description>
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/

</description>
    <dc:creator>M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-12T20:23:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1232">
    <title>Speeding up ODBC Connection</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1232</link>
    <description>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

</description>
    <dc:creator>Minh-Long Pham</dc:creator>
    <dc:date>2008-09-12T19:49:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1231">
    <title>Re: How to bypass ODBC Manager (iODBC or unixODBC)to use freetds driverConnector?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1231</link>
    <description>
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 t</description>
    <dc:creator>M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-11T21:43:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1230">
    <title>How to bypass ODBC Manager (iODBC or unixODBC) to use freetds driver Connector?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1230</link>
    <description>
_______________________________________________________________________
eGenix.com User Mailing List                     http://www.egenix.com/
https://www.egenix.com/mailman/listinfo/egenix-users
</description>
    <dc:creator>kw_dev_lists-maGkBM8SPcwgA6DENJS+mtBPR1lH4CV8&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2008-09-11T19:21:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1229">
    <title>Re: cursor.executedirect configurable?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1229</link>
    <description>
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</description>
    <dc:creator>M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-11T17:44:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1228">
    <title>Re: cursor.executedirect configurable?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1228</link>
    <description>
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.

</description>
    <dc:creator>Brad Allen</dc:creator>
    <dc:date>2008-09-11T15:28:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1227">
    <title>Re: cursor.executedirect configurable?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1227</link>
    <description>
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() ?

</description>
    <dc:creator>M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-11T10:08:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1226">
    <title>Re: cursor.executedirect configurable?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1226</link>
    <description>
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.


</description>
    <dc:creator>M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-10T15:23:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1225">
    <title>Re: cursor.executedirect configurable?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1225</link>
    <description>
_______________________________________________________________________
eGenix.com User Mailing List                     http://www.egenix.com/
https://www.egenix.com/mailman/listinfo/egenix-users
</description>
    <dc:creator>Brad Allen</dc:creator>
    <dc:date>2008-09-10T13:48:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1224">
    <title>Re: cursor.executedirect configurable?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1224</link>
    <description>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 </description>
    <dc:creator>M.-A. Lemburg</dc:creator>
    <dc:date>2008-09-10T09:13:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1223">
    <title>cursor.executedirect configurable?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1223</link>
    <description>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.

</description>
    <dc:creator>Brad Allen</dc:creator>
    <dc:date>2008-09-10T02:18:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.egenix.user/1222">
    <title>Re: [mxTidy/MacOSX] _CleanTree error</title>
    <link>http://permalink.gmane.org/gmane.comp.python.egenix.user/1222</link>
    <description>

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

</description>
    <dc:creator>Darryl Cousins</dc:creator>
    <dc:date>2008-09-05T20:31:42</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.python.egenix.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.python.egenix.user</link>
  </textinput>
</rdf:RDF>
