An error occurred fetching the project authors.
- 07 Jun, 2006 1 commit
-
-
evgen@moonbone.local authored
The st_lex::which_check_option_applicable() function controls for which statements WITH CHECK OPTION clause should be taken into account. REPLACE and REPLACE_SELECT wasn't in the list which results in allowing REPLACE to insert wrong rows in a such view. The st_lex::which_check_option_applicable() now includes REPLACE and REPLACE_SELECT in the list of statements for which WITH CHECK OPTION clause is applicable.
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 05 Apr, 2005 1 commit
-
-
serg@serg.mylan authored
fix a race condition in TC_LOG_BINLOG::unlog
-
- 10 Dec, 2003 1 commit
-
-
Deprecate the use of TYPE=... Preferred syntax is ENGINE=
-
- 22 Jan, 2003 1 commit
-
-
hf@deer.mysql.r18.ru authored
DEFAULT in SELECT & UPDATE corrections
-
- 05 Jan, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Cleaned up test; Removed wrong DROP TABLE commands and use standard table and database names. changed store_warning() -> push_warning_print()
-
- 06 Mar, 2001 1 commit
-
-
monty@donna.mysql.fi authored
Remember UNION for ALTER TABLE Added test for if we are supporting transactions. Don't allow REPLACE to replace a row when we have generated an auto_increment key Fixed bug when using BLOB keys Fixed bug in SET @variable=user.
-
- 27 Dec, 2000 1 commit
-
-
monty@donna.mysql.com authored
Fixed test results. Added mysqld variable 'have_isam'
-
- 22 Dec, 2000 1 commit
-
-
tim@cane.mysql.fi authored
-
- 21 Dec, 2000 1 commit
-
-
tim@cane.mysql.fi authored
Test delete from BDB table using hidden primary key.
-