4 Commits

Author	SHA1	Message	Date
Ulf Wendel	776d1e5ece	New utility function to check for '[1148] The used command is not allowed with this MySQL version' during SKIPIF	2011-08-31 13:50:58 +00:00
Ulf Wendel	d920185b9c	Check if server supports LOAD DATA LOCAL INFILE to catch [1148] The used command is not allowed with this MySQL version during SKIPIF	2011-08-31 12:58:25 +00:00
Ulf Wendel	e123cae8ac	Proxying as many connect calls as possible to make testing of the compression protocol @ mysqlnd easier. By setting the environment variable MYSQL_TEST_COMPRESS you can tell the tests to set the MYSQLI_CLIENT_COMPRESS flag upon connect.	2009-09-24 12:51:03 +00:00
Ulf Wendel	1b5f0f63b4	Fix (by Andrey) and test for bug #49442 . Don't use efree() for memory allocated with malloc()... If a connection gets created by mysqli_init(), mysqlnd makes it 'persistent'. 'Persistent' means that mysqlnd uses malloc(). mysqlnd does use malloc() instead of ealloc() because it is unknown if the connection will become a true persistent connection in the sense of ext/mysqli. It is unknown if the user wants a persistent connection or not until the user calls mysqli_real_connect(). To avoid tricky conversions mysqlnd uses malloc(), which sets a private persistent flag in the mysqlnd structures. A precondition for the crash to happen was that the private persistent flag is set. The flag is also set when creating a real persistent connection (in the sense of ext/mysqli) and so the bug can happen with mysql_init()/mysqli_real_connect() and mysql_connect('p:<host>', ...). Therefore we test both cases. Note the (tricky?) difference between the implementation detail'mysqlnd private persistent flag = use malloc()' and persistent connections from a user perspective. Although mysqlnd will always set its private persistent flag and use malloc() for connections created with mysqli_init() it is still up to the user to decide in mysqli_real_connect() if the connection shall become a (true) persistent connection or not.	2009-09-16 17:03:44 +00:00