1
0
mirror of https://github.com/MariaDB/server.git synced 2026-01-06 05:22:24 +03:00

New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support

Added new tests and corrected existing tests


mysql-test/suite/stress/include/ddl3.inc:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
  
  Had to change CREATE TABLE statements to include NOT NULL due to CSV engine constraints
mysql-test/suite/stress/r/ddl_archive.result:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
  
  Reproduced .result files due to changes in ddl3.inc
mysql-test/suite/stress/r/ddl_csv.result:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
  
  Reproduced .result files due to changes in ddl3.inc
mysql-test/suite/stress/r/ddl_innodb.result:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
  
  Reproduced .result files due to changes in ddl3.inc
mysql-test/suite/stress/r/ddl_memory.result:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
  
  Reproduced .result files due to changes in ddl3.inc
mysql-test/suite/stress/r/ddl_myisam.result:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
  
  Reproduced .result files due to changes in ddl3.inc
mysql-test/suite/stress/r/ddl_ndb.result:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
  
  Reproduced .result files due to changes in ddl3.inc
BitKeeper/etc/ignore:
  Added mysql-test/.DS_Store .DS_Store to the ignore list
mysql-test/t/disabled.def:
  Disabled new test - csv_alter_table.test file due to Bug#33696.
  
  Cannot generate a .result file due to the Bug.  These tests can be enabled to test the bug fix without needing new tests unless the developer feels the need to add more.
mysql-test/r/csv_not_null.result:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
mysql-test/t/csv_alter_table.test:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
  
  Designed to test fixes for Bug#33696 - CSV Engine allows nullable columns via ALTER TABLE statements
mysql-test/t/csv_not_null.test:
  New tests added for Bug#33558 - Test "stress.ddl_csv needs nullable columns which CSV does not support
This commit is contained in:
unknown
2008-01-21 13:49:03 -05:00
parent ed2ab9338e
commit 63c73b52f3
12 changed files with 273 additions and 49 deletions

View File

@@ -0,0 +1,106 @@
#-----------------------------------------------------------------------------
# csv_not_null.test - .test file for MySQL regression suite
# Purpose: To test the behavior of the CSV engine
# Bug#31473 resulted in strict enforcement of non-nullable
# columns in CSV engine.
# NOTE: Main functionality tested - NOT NULL restrictions on CSV tables
# CREATE, INSERT, and UPDATE statements
# ALTER statements in separate file due to BUG#33696
# Author pcrews
# Last modified: 2008-01-04
#-----------------------------------------------------------------------------
--source include/have_csv.inc
#############################################################################
# Testcase csv_not_null.1: CREATE TABLE for CSV Engine requires explicit
# NOT NULL for each column
#############################################################################
-- echo # ===== csv_not_null.1 =====
-- disable_warnings
DROP TABLE IF EXISTS t1, t2;
-- enable_warnings
--echo # === Will fail -- no NOT NULL ===
--error ER_CHECK_NOT_IMPLEMENTED
CREATE TABLE t1 (a int) ENGINE = CSV;
--echo # === Good CREATE ===
CREATE TABLE t1 (a int NOT NULL) ENGINE = CSV;
--echo # === Will fail -- ALL columns need NOT NULL ==
--error ER_CHECK_NOT_IMPLEMENTED
CREATE TABLE t2 (a int NOT NULL, b char(20)) ENGINE = CSV;
DROP TABLE t1;
##############################################################################
# Testcase csv_not_null.2: INSERT tests -- validating behavior of INSERT
# statements for CSV
##############################################################################
-- echo # ===== csv_not_null.2 =====
-- disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings
CREATE TABLE t1 (a int NOT NULL, b blob NOT NULL, c CHAR(20) NOT NULL,
d VARCHAR(20) NOT NULL, e enum('foo','bar') NOT NULL,f DATE NOT NULL)
ENGINE = CSV;
-- echo # === should result in default for each datatype ===
-- disable_warnings
INSERT INTO t1 VALUES();
-- enable_warnings
SELECT * FROM t1;
-- disable_warnings
# NOTE - Test disabled due to enum crash for this INSERT
# See Bug#33717 - INSERT...(default) fails for enum.
# Crashes CSV tables, loads spaces for MyISAM
#INSERT INTO t1 VALUES(default,default,default,default,default,default);
-- enable_warnings
SELECT * FROM t1;
INSERT INTO t1 VALUES(0,'abc','def','ghi','bar','1999-12-31');
SELECT * FROM t1;
-- echo # === insert failures ===
--error ER_BAD_NULL_ERROR
INSERT INTO t1 VALUES(NULL,'ab','a','b','foo','2007-01-01');
--error ER_NO_DEFAULT_FOR_FIELD
INSERT INTO t1 VALUES(default(a),default(b), default(c), default(d),
default(e), default(f));
DROP TABLE t1;
##############################################################################
# Testcase csv_not_null.3: UPDATE tests -- examining behavior of UPDATE
# statements for CSV
# NOTE: Should not allow UPDATE <table> set <NOT_NULL_COLUMN> = NULL
# WHERE <condition>;
# However, this is currently allowed -- <NOT_NULL_COLUMN> is
# set to the default value for the given datatype
# Might have to change this test depending on the action taken for
# Bug#33699 (addressing this behavior)
##############################################################################
-- echo # ===== csv_not_null.3 =====
-- disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings
CREATE DATABASE csv_not_null_test;
USE csv_not_null_test;
CREATE TABLE t1 (a int NOT NULL, b char(10) NOT NULL) ENGINE = CSV;
INSERT INTO t1 VALUES();
SELECT * FROM t1;
UPDATE t1 set b = 'new_value' where a = 0;
SELECT * FROM t1;
# Might need to change this depending on Bug#33699 -UPDATE allows NULL
# as new value on NOT NULL columns (= default datatype value)
# Currently sets to datatype default -- might throw error
UPDATE t1 set b = NULL where b = 'new_value';
SELECT * FROM t1;
DROP TABLE t1;