> At a small glance, your code looks OK. Try looking at resulting string
> sql in gdb or just print it out to stdout. That might catch your bug.
>
Thanks again for the reply. The query looks sane.. As I mentioned, I
spit it out to a file and piped it directly to mysql (after inspecting
it). At least where it truncates there isn't anything abnormal (the blob
is merely a tab delimited string of ints) and the same truncation occurs.
> MySQL commands lenghts are limited only by max_allowed_packet, which
> can be extended up to 16 Mb in 3.23 and 4 Gb in 4.0.
>
Nodz.. that's what I thought. This is our setting:
set-variable = max_allowed_packet=7096128
Confirmed in variables:
| max_allowed_packet | 7095296
It's definately not that big, and, we aren't getting the standard expected
errors when you exceed packet size (such as mysql server has gone away).
The only clue we have is this:
010624 19:44:23 Aborted connection 231 to db: 'unconnected' user: 'root'
host: `localhost' (Got timeout reading communication packets)
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
