On 04/03/2018 06:15 PM, Sebastien FLAESCH wrote:
On 04/03/2018 05:59 PM, Sebastien FLAESCH wrote:
Hi all,
Looking for some configuration tips to speed execution of our non-regression
tests with MySQL.
We do pure functional testing, data persistence is not critical.
Our tests are not using a
On 04/03/2018 05:59 PM, Sebastien FLAESCH wrote:
Hi all,
Looking for some configuration tips to speed execution of our non-regression
tests with MySQL.
We do pure functional testing, data persistence is not critical.
Our tests are not using a lot of data, but we create and drop a lot of test
Hi all,
Looking for some configuration tips to speed execution of our non-regression
tests with MySQL.
We do pure functional testing, data persistence is not critical.
Our tests are not using a lot of data, but we create and drop a lot of test
tables.
We have concurrency tests (processes loc
Can you please stop using C++ comments in header files designed for C
programming?
/opt3/dbs/mys/8.0/include/mysql.h:36:1: error: C++ style comments are not
allowed in ISO C90 [-Werror]
// Small extra definitions to avoid pulling in my_inttypes.h in client code.
^
/opt3/dbs/mys/8.0/include/my
Sorry for the spam, and thanks for you suggestion Johan!
http://bugs.mysql.com/bug.php?id=84470
Seb
On 01/11/2017 11:21 AM, Johan De Meersman wrote:
Seb,
You should log a bug at http://bugs.mysql.com - this is not a developer list.
/Johan
- Original Message -
From: "Seba
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
*) &ct);
Then it works ...
Seb
On 01/10/2017 02:55 PM, Sebastien FLAESCH wrote:
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
con
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.
T
I did the following test:
My program still uses MySQL 5.7 libmysqlclient.so, but I connect now to a
5.6.16 server.
And the SQL interrupt works fine... so I suspect there is a MySQL server issue
in 5.7.
Seb
On 07/12/2016 01:01 PM, Sebastien FLAESCH wrote:
About:
> B) For some reason,
hangs in recvfrom():
recvfrom(3,
On 07/03/2016 06:55 PM, Sebastien FLAESCH wrote:
Hi all,
I use the following technique to cancel a long running query:
In the SIGINT signal handler, I restart a connection and I perform a
KILL QUERY mysql-process-id-of-running-query
This was working f
Hi all,
I use the following technique to cancel a long running query:
In the SIGINT signal handler, I restart a connection and I perform a
KILL QUERY mysql-process-id-of-running-query
This was working find with MySQL 5.6.
But with 5.7 (5.7.11), we get now a different result:
A) The query
ULL
|
++-+-+---+-+--+--+--+
Why it is in "Sleep" state?!?
Seb
On 06/21/2016 06:27 PM, Sebastien FLAESCH wrote:
FYI, I get the same problem with MySQL 5.7.13.
Seb
On 06/21/2016 04:59 PM, Sebastien FLAESCH wrote:
Seems that after KILL QUERY mysql-thread-id, a call to
mysql_stmt_clos
FYI, I get the same problem with MySQL 5.7.13.
Seb
On 06/21/2016 04:59 PM, Sebastien FLAESCH wrote:
Seems that after KILL QUERY mysql-thread-id, a call to
mysql_stmt_close(stmt-handle) hangs...
This did not happen in 5.6 ...
Will try 5.7.13 ...
Seb
On 06/21/2016 04:03 PM, Sebastien
Seems that after KILL QUERY mysql-thread-id, a call to
mysql_stmt_close(stmt-handle) hangs...
This did not happen in 5.6 ...
Will try 5.7.13 ...
Seb
On 06/21/2016 04:03 PM, Sebastien FLAESCH wrote:
Hi all,
The technique described in this thread is working fine with MySQL 5.6
ysql> \q
Bye
Thanks!
Seb
On 12/03/2014 05:25 PM, Sebastien FLAESCH wrote:
Hi all,
I have a similar question regarding KILL QUERY usage:
We have a C client program using libmysqlclient.so, it is a single-threaded
program.
When running a long query, how can I send the KILL QUERY command wh
Hi all,
In version 5.7.10, I found a C++ comment in the .h headers:
#endif // __cplusplus
Should be:
#endif /* __cplusplus */
To avoid:
cc -g -fsanitize=address -fno-omit-frame-pointer -W -Wall -pedantic
-Wmissing-prototypes \
-Wno-long-long -Werror -fPIC \
-I/opt3/dbs/mys/5.7/include
do the job...
Thanks.
Seb
On 12/12/2014 12:12 PM, rafal somla wrote:
Hello Sebastein,
On 2014-12-03 17:25, Sebastien FLAESCH wrote:
Hi all,
I have a similar question regarding KILL QUERY usage:
We have a C client program using libmysqlclient.so, it is a
single-threaded program.
When running a
Nobody concerned by this case?
Simple question: is it safe or not to do a KILL QUERY in a SIGINT signal
handler?
S.
On 12/03/2014 05:25 PM, Sebastien FLAESCH wrote:
Hi all,
I have a similar question regarding KILL QUERY usage:
We have a C client program using libmysqlclient.so, it is a
Hi all,
I have a similar question regarding KILL QUERY usage:
We have a C client program using libmysqlclient.so, it is a single-threaded
program.
When running a long query, how can I send the KILL QUERY command when a SIGINT
(CTRL-C)
is caught? (of course we implement a signal handler, so we
Hello,
On 07/31/2013 01:03 PM, Sunanda Menon wrote:
> * The C API libmysqlclient shared-library .so files now have
> version 18.1.0 (up from version 18.0.0 used in MySQL 5.5).
> (Bug #16809055)
What impact has this change regarding backward compatibility with
existing C pro
On 05/17/2013 03:07 PM, Reindl Harald wrote:
Am 17.05.2013 14:53, schrieb Sebastien FLAESCH:
On 05/17/2013 12:29 PM, Reindl Harald wrote:
Am 17.05.2013 12:05, schrieb Sebastien FLAESCH:
Beside the Oracle skills debate and the stupid mistakes with soname
changes between 5.5.8 and 5.5.10 or
On 05/17/2013 12:29 PM, Reindl Harald wrote:
Am 17.05.2013 12:05, schrieb Sebastien FLAESCH:
Beside the Oracle skills debate and the stupid mistakes with soname
changes between 5.5.8 and 5.5.10 or 5.6.x, (imagine all of this did
not happen):
I have a VERY simple question that needs a VERY
5.5.10 and earlier 5.5 versions, so client programs that
use the 5.5 client library should be recompiled against the 5.5.10 client
library. (Bug #60061, Bug #11827366)
Am 17.05.2013 11:10, schrieb Sebastien FLAESCH:
Could someone from the libmysqlclient contributors comment on this, and
could someone
Hi all,
Could someone from the libmysqlclient contributors comment on this, and
could someone complete the documentation regarding client compatiblity?
Thanks!
Seb
On 02/20/2013 09:31 AM, Sebastien FLAESCH wrote:
Hello,
FYI, I found this statement in the doc, at the end of the C API main
Hello,
FYI, I found this statement in the doc, at the end of the C API main page:
http://dev.mysql.com/doc/refman/5.6/en/c.html
If, after an upgrade, you experience problems with compiled client programs, such as Commands out of sync or unexpected core dumps, you probably have
used old header
On 02/18/2013 12:14 PM, Noel Butler wrote:
On Mon, 2013-02-18 at 10:57 +0100, Sebastien FLAESCH wrote:
I have several versions of MySQL installed on my Linux, and it appears
that the libmysqlclient versions have changed in the 5.x version line:
/opt3/dbs/mys/4.1.24/lib/libmysqlclient.so.14
Hi all,
What is the compatibility policy regarding the MySQL C API library?
I could not find the rules in the documentation.
I have several versions of MySQL installed on my Linux, and it appears
that the libmysqlclient versions have changed in the 5.x version line:
/opt3/dbs/mys/4.1.24/lib/li
27 matches
Mail list logo
