stien FLAESCH" <s...@4js.com>
To: "MySql" <mysql@lists.mysql.com>
Sent: Tuesday, 10 January, 2017 14:55:42
Subject: kill query and prepared statements
Hi all,
I have reported this problem before, but I raise it again, since I still get
this problem with 5.7.17
See att
Seb,
You should log a bug at http://bugs.mysql.com - this is not a developer list.
/Johan
- Original Message -
> From: "Sebastien FLAESCH" <s...@4js.com>
> To: "MySql" <mysql@lists.mysql.com>
> Sent: Tuesday, 10 January, 2017 14:55:42
> Subje
Just to be clear:
This is a hint, to find the real problem, this is NOT A WORKAROUND for us!
Seb
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
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 *)
Hi all,
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.
