4 commits

Author	SHA1	Message	Date
thek@kpdesk.mysql.com	19dfc42eb6	Bug#23240 --init_file statements with NOW() reports '1970-01-01 11:00:00'as the date time ... - Starting time of a query sent by bootstrapping wasn't initialized and starting time defaulted to 0. This later used value by NOW- item and was translated to 1970-01-01 11:00:00. - Marketing the time with thd->set_time() before the call to mysql_parse resolves this issue. - set_time was refactored to be part of the thd->init_for_queries- process.	2007-02-19 14:57:54 +01:00
konstantin@mysql.com	b99e11c8bd	A fix and a test case for Bug#17843 "Certain stored procedures fail to ... run at startup" The server returned an error when trying to execute init-file with a stored procedure that could return multiple result sets to the client. A stored procedure can return multiple result sets if it contains PREPARE, SELECT, SHOW and similar statements. The fix is to set client_capabilites|=CLIENT_MULTI_RESULTS in sql_parse.cc:handle_bootstrap(). There is no "client" really, so nothing is ever sent. This makes init-file feature behave consistently: the prepared statements that can be called directly in the init-file can be used in a stored procedure too. Re-committed the patch originally submitted by Per-Erik after review.	2006-07-04 23:46:15 +04:00
serg@sergbook.mylan	606073084e	symlink, not hardlink ... mkdir in Makefile, not in configure chmod a-x	2004-04-21 14:55:39 -05:00
lenz@mysql.com	e306876fe1	- renamed mysql-test/t/init_file.sql to mysql-test/std_data/init_file.dat ... so it gets picked up by "make dist" and updated init_file test accordingly.	2004-02-05 23:36:54 +01:00

Renamed from mysql-test/t/init_file.sql (Browse further)