Skip to content
This repository has been archived by the owner on Feb 22, 2020. It is now read-only.

Still got "Socket receive buffer full" exception #34

Open
yihuang opened this issue Jun 24, 2013 · 3 comments
Open

Still got "Socket receive buffer full" exception #34

yihuang opened this issue Jun 24, 2013 · 3 comments

Comments

@yihuang
Copy link

yihuang commented Jun 24, 2013

I have a table which has a blob field, and when i want to query all data from it, i got "Socket receive buffer full".
And when i increase the MYSQL_PACKET_SIZE from (1024 * 1024 * 16) to (1024 * 1024 * 32), it's disappeared.

alldata = list(executeSQL('select * from table_with_big_blob_field', ()).rows)
@jskorpan
Copy link

That is expected. The umysql driver doesn't use streaming but instead retreives the entire result set in memory.

//JT

On 24 jun 2013, at 15:03, "yihuang" <notifications@github.commailto:notifications@github.com> wrote:

I have a table which has a blob field, and when i want to query all data from it, i got "Socket receive buffer full".
And when i increase the MYSQL_PACKET_SIZE from (1024 * 1024 * 16) to (1024 * 1024 * 32), it's disappeared.

alldata = list(executeSQL('select * from table_with_big_blob_field', ()).rows)`


Reply to this email directly or view it on GitHubhttps://github.com//issues/34.

@V-E-O
Copy link

V-E-O commented Jun 27, 2013

This figure has related to query size too big problem? If so, can this figure be able to set when build the connection? In some environment, large query is needed and query size is controlled by server-side.

@jkbbwr
Copy link

jkbbwr commented Jul 10, 2013

This issue still exists, can you please provide a solution that allows users to run queries on sets larger than your buffer size without manually setting limits in SQL

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants