[egenix-users] Problems with number of results being returned

[Dev Sen]

Charlie,

Thanks for your response. My next line of inquiry was going to be the ODBC
adaptor. I am actually using Actual's ODBC driver for Mac so I will try the
MySQL one and see if that fixes the issue.

I haven't set the limits either in the ZMI or through SQL. On my colleague's
Windows machine the 5,000 results sets return very quickly, so timeout isn't
an issue. 

If I find the problem is with the ODBC driver I'll repost to this list just
in case anyone else has the same problem in the future.

Dev  


On 4/5/07 4:09 PM, "Charlie Clark" <charlie at egenix.com> wrote:

> Am 05.04.2007, 20:28 Uhr, schrieb Dev Sen <DEV.K.SEN at saic.com>:
> 
>> Hi,
>> This is my first post to the list, so I hope my question isn¹t too naïve.
>> I am developing a database app in Zope/Plone using MySQL with the egenix
>> DB
>> adaptor on a Mac Pro. So far everything with the adaptor has been good,
>> although I am now having strange issues. I have some queries which return
>> around 5,000 rows of data. When I run the query with parameters so that
>> only
>> 1200 or so rows are returned there is no problem, however, for larger
>> result
>> sets I get an error saying the connection to the database was lost.
>> Another
>> developer working on the same project (identical code, software versions)
>> but running Windows XP doesn¹t have this problem at all. Also, running
>> the
>> queries directly in MySQL works fine. Therefore we think it has
>> something to
>> do with the Mac OSX version of the egenix DB adaptor.
>> Has anyone seen this behavior before? Is this a known bug?
> 
> Dev,
> 
> I believe that MySQL has only just released their ODBC driver for Mac OS X
> and this is where we suspect the problem is so it's probably a good idea
> to make sure you have the most uptodate version of this driver. As for
> limiting the number of rows returned. Are you doing this through the
> advanced tab in the ZSQL method or through LIMIT in the SQL statement?
> MySQL (MyASM tables) can be unbelievably slow on certain types of query
> such as ANSI INNER JOINS or subselects but if you enforce a hard LIMIT in
> your SQL there should be no reason for a timeout as maybe happening here.
> 
> Charlie Clark