Re: kill query and prepared statements
- Date: Tue, 10 Jan 2017 18:00:21 +0100
- From: Sebastien FLAESCH <sf@xxxxxxx>
- Subject: Re: kill query and prepared statements
Just to be clear:
This is a hint, to find the real problem, this is NOT A WORKAROUND for us!
On 01/10/2017 03:53 PM, Sebastien FLAESCH wrote:
Investigating different API calls, to see if it makes a difference...
Seems that the problem is related to the read-only cursor type option!
If you comment out:
unsigned long ct = (unsigned long) CURSOR_TYPE_READ_ONLY;
s = mysql_stmt_attr_set(stmt, STMT_ATTR_CURSOR_TYPE, (const void *) &ct);
Then it works ...
On 01/10/2017 02:55 PM, Sebastien FLAESCH wrote:
I have reported this problem before, but I raise it again, since I still get this problem with 5.7.17
See attached code:
I want to interrupt a long running statement with CTRL-C by starting a new connect to make a KILL QUERY.
I am using the same technique as the mysql client code.
The difference here is that my code is using PREPARED STATEMENTS with mysql_stmt_prepare() etc.
Problem: After interrupting the first query with CTRL-C, the call to mysql_stmt_close() hangs...
Maybe I am missing some new connection or statement option...?!?
IMPORTANT: This problem appeared in a 5.7.x, same code is working fine with 5.6(.16) !!!!
Please can someone from MySQL C API team try to reproduce and confirm?
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql