Here's the resolution to this problem.

In odbc.ini add::
Option     = 2097152

"Force the use of Forward-only cursor type. In case of applications setting the default static/dynamic cursor type, and one wants the driver to use non-cache result sets, then this option ensures the forward-only cursor behavior."

See also my bug report:

http://bugs.mysql.com/bug.php?id=19439

bill
On May 1, 2006, at 9:47 AM, Robert Garcia wrote:

I am using longblobs, on these fields, don't know if that makes a diff, and mysql 5.0.18 with FC5.

--

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/

On May 1, 2006, at 9:39 AM, William M Conlon wrote:

Sorry for the scare. I think this problem is a regression. It wasn't present in 3.23. And actually I don't think it appeared until recently (I run yum update once a month or so). I moved my dev server to FC4 about 6 months ago and I'm pretty sure I checked everything -- I use the swish-e spider as an automated tester, and I have a tcf error reported that emails me app errors. Well on dev, I don't run the spider under cron. But after six months, I thought it was safe to update production from FC3 (with mysql3.23) to FC4 (with mysql4.1.16-1-fc4). Anyway, I got error reports when the spider ran on production.

Until I have a fix, I'm just going to have to restrict my selects to row sizes less than 4 MB.


On May 1, 2006, at 12:42 AM, Robert Garcia wrote:

Well you scared me a bit, cuz we are just launching our hirez upload system. I just tested, with 50meg tiffs. No problem on upload or download. Witango using 3.51 myodbc, big results on.

I watch processor and mem on 14 meg image download via witango, didn't even spike, I had to check if I did it right. IIS 6/2003/ Witango, didn't even sweat it.

--

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/

On Apr 30, 2006, at 10:44 AM, William M Conlon wrote:

Hmm, I'm pretty sure it's unrelated to odbc, since the mysql client fails from the command line when executing the query. I've filed a bug report with mysql.

Yes max_allowed_packet needs to be set. The default for the server is 1M, but for the client it's 16M. Watching top while the query is run, you see mysql (client, as opposed to mysqld) run up from 16M to >1000M, whereupon it errors out.

Same behavior whether the query is run from the command line or witango. Interestingly webmin can download the problematic blobs. My webmin is configured to use DBI, so the perl interface works. I presume DBI::DBD::mysql hooks to the C api rather than using the mysql client. Of course it makes me wonder why unixODBC uses the mysql client instead of the C api, but that's another issue, but potentially relevant to you witango/php performance comparison. I think php uses the C api.

Re apache2, I guess I'll have to compile and test it with witango.


thx.
On Apr 29, 2006, at 5:59 PM, Robert Garcia wrote:

no, but am running php5 with apache2.2.

Did you check that the option in mysqlodbc 3.51 allow big results is checked?

And I think there may be a parameter we set on the server side.

I will run a test or two on some bigger blobs.

--

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/

On Apr 29, 2006, at 3:57 PM, William M Conlon wrote:

I'm having a problem with mysql 4.1.16-1-fc4. The client blows up -- out of memory -- when reading medium blobs larger than around 4.2 MB. This first showed up as a Witango ODBC error, but I ran the mysql client from the shell and confirmed it's a mysql problem.

So my questions:
1. anyone running mysql-4.1.18 who can confirm whether the problem still exists? It's not available as an rpm for FC4 yet, but I could build from source if needed. 2. I know Robert Garcia is running mysql 5 and retrieving blobs. anyone else? What version of mysql?

3. Robert, You're running FC5 and apache 2.2. Have you tried running Witango 5 with apache 2.2?

Thanks.

Bill

William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
   vox:  650.327.2175 (direct)
   fax:  650.329.8335
mobile:  650.906.9929
e-mail:  mailto:[EMAIL PROTECTED]
   web:  http://www.tothept.com

_________________________________________________________________ _______ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/ maillist.taf


__________________________________________________________________ ______ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/ maillist.taf

Bill

William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
   vox:  650.327.2175 (direct)
   fax:  650.329.8335
mobile:  650.906.9929
e-mail:  mailto:[EMAIL PROTECTED]
   web:  http://www.tothept.com

___________________________________________________________________ _____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf


____________________________________________________________________ ____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Bill

William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
   vox:  650.327.2175 (direct)
   fax:  650.329.8335
mobile:  650.906.9929
e-mail:  mailto:[EMAIL PROTECTED]
   web:  http://www.tothept.com

_____________________________________________________________________ ___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf


______________________________________________________________________ __
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Bill

William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
   vox:  650.327.2175 (direct)
   fax:  650.329.8335
mobile:  650.906.9929
e-mail:  mailto:[EMAIL PROTECTED]
   web:  http://www.tothept.com

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to