#
# test of already fixed bugs
#
--disable_warnings
drop table if exists t1,t2,t3,t4,t5,t6;
drop database if exists mysqltest;
SET sql_mode = 'NO_ENGINE_SUBSTITUTION';
#
# Bug 10838
# Insert causes warnings for no default values and corrupts tables
#
CREATE TABLE t1 (a varchar(30) binary NOT NULL DEFAULT ' ',
                 b varchar(1) binary NOT NULL DEFAULT ' ',
		 c varchar(4) binary NOT NULL DEFAULT '0000',
		 d tinyblob NULL,
		 e tinyblob NULL,
		 f tinyblob NULL,
		 g tinyblob NULL,
		 h tinyblob NULL,
		 i tinyblob NULL,
		 j tinyblob NULL,
		 k tinyblob NULL,
		 l tinyblob NULL,
		 m tinyblob NULL,
		 n tinyblob NULL,
		 o tinyblob NULL,
		 p tinyblob NULL,
                 q varchar(30) binary NOT NULL DEFAULT ' ',
                 r varchar(30) binary NOT NULL DEFAULT ' ',
		 s tinyblob NULL,
                 t varchar(4) binary NOT NULL DEFAULT ' ',
                 u varchar(1) binary NOT NULL DEFAULT ' ',
                 v varchar(30) binary NOT NULL DEFAULT ' ',
                 w varchar(30) binary NOT NULL DEFAULT ' ',
		 x tinyblob NULL,
                 y varchar(5) binary NOT NULL DEFAULT ' ',
                 z varchar(20) binary NOT NULL DEFAULT ' ',
                 a1 varchar(30) binary NOT NULL DEFAULT ' ',
		 b1 tinyblob NULL)
ENGINE=InnoDB DEFAULT CHARACTER SET = latin1 COLLATE latin1_bin;
--enable_warnings

INSERT into t1 (b) values ('1');
SHOW WARNINGS;
SELECT * from t1;

CREATE TABLE t2 (a varchar(30) binary NOT NULL DEFAULT ' ',
                 b varchar(1) binary NOT NULL DEFAULT ' ',
		 c varchar(4) binary NOT NULL DEFAULT '0000',
		 d tinyblob NULL,
		 e tinyblob NULL,
		 f tinyblob NULL,
		 g tinyblob NULL,
		 h tinyblob NULL,
		 i tinyblob NULL,
		 j tinyblob NULL,
		 k tinyblob NULL,
		 l tinyblob NULL,
		 m tinyblob NULL,
		 n tinyblob NULL,
		 o tinyblob NULL,
		 p tinyblob NULL,
                 q varchar(30) binary NOT NULL DEFAULT ' ',
                 r varchar(30) binary NOT NULL DEFAULT ' ',
		 s tinyblob NULL,
                 t varchar(4) binary NOT NULL DEFAULT ' ',
                 u varchar(1) binary NOT NULL DEFAULT ' ',
                 v varchar(30) binary NOT NULL DEFAULT ' ',
                 w varchar(30) binary NOT NULL DEFAULT ' ',
		 x tinyblob NULL,
                 y varchar(5) binary NOT NULL DEFAULT ' ',
                 z varchar(20) binary NOT NULL DEFAULT ' ',
                 a1 varchar(30) binary NOT NULL DEFAULT ' ',
		 b1 tinyblob NULL)
DEFAULT CHARACTER SET = latin1 COLLATE latin1_bin;

SHOW CREATE TABLE t2;
INSERT into t2 (b) values ('1');
SHOW WARNINGS;
SELECT * from t2;

drop table t1;
drop table t2;


#
# Bug#20691: DATETIME col (NOT NULL, NO DEFAULT) may insert garbage when specifying DEFAULT
#
# From the docs:
#  If the column can take NULL as a value, the column is defined with an
#  explicit DEFAULT NULL clause. This is the same as before 5.0.2.
#
#  If the column cannot take NULL as the value, MySQL defines the column with
#  no explicit DEFAULT clause. For data entry, if an INSERT or REPLACE
#  statement includes no value for the column, MySQL handles the column
#  according to the SQL mode in effect at the time:
#
#    * If strict SQL mode is not enabled, MySQL sets the column to the
#      implicit default value for the column data type.
#
#    * If strict mode is enabled, an error occurs for transactional tables and
#      the statement is rolled back. For non-transactional tables, an error
#      occurs, but if this happens for the second or subsequent row of a
#      multiple-row statement, the preceding rows will have been inserted.
#
create table bug20691 (i int, d datetime NOT NULL, dn datetime not null default '0000-00-00 00:00:00');
insert into bug20691 values (1, DEFAULT, DEFAULT), (1, '1975-07-10 07:10:03', '1978-01-13 14:08:51'), (1, DEFAULT, DEFAULT);
insert into bug20691 (i) values (2);
desc bug20691;
insert into bug20691 values (3, DEFAULT, DEFAULT), (3, '1975-07-10 07:10:03', '1978-01-13 14:08:51'), (3, DEFAULT, DEFAULT);
insert into bug20691 (i) values (4);
insert into bug20691 values (5, DEFAULT, DEFAULT), (5, '1975-07-10 07:10:03', '1978-01-13 14:08:51'), (5, DEFAULT, DEFAULT);
SET sql_mode = 'ALLOW_INVALID_DATES';
insert into bug20691 values (6, DEFAULT, DEFAULT), (6, '1975-07-10 07:10:03', '1978-01-13 14:08:51'), (6, DEFAULT, DEFAULT);
SET sql_mode = default;
--error 1364
insert into bug20691 values (7, DEFAULT, DEFAULT), (7, '1975-07-10 07:10:03', '1978-01-13 14:08:51'), (7, DEFAULT, DEFAULT);
select * from bug20691 order by i asc;
drop table bug20691;

SET sql_mode = '';
create table bug20691 (
  a set('one', 'two', 'three') not null,
  b enum('small', 'medium', 'large', 'enormous', 'ellisonego') not null,
  c time not null,
  d date not null,
  e int not null,
  f long not null,
  g blob not null,
  h datetime not null,
  i decimal not null,
  x int);
insert into bug20691 values (2, 3, 5, '0007-01-01', 11, 13, 17, '0019-01-01 00:00:00', 23, 1);
insert into bug20691 (x) values (2);
insert into bug20691 values (2, 3, 5, '0007-01-01', 11, 13, 17, '0019-01-01 00:00:00', 23, 3);
insert into bug20691 values (DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, 4);
select * from bug20691 order by x asc;
drop table bug20691;

create table t1 (id int not null);
insert into t1 values(default);

create view v1 (c) as select id from t1;
insert into t1 values(default);
drop view v1;
drop table t1;

#
# Bug #39002: crash with
#             INSERT ... SELECT ... ON DUPLICATE KEY UPDATE col=DEFAULT
#

create table t1 (a int unique);
create table t2 (b int default 10);
insert into t1 (a) values (1);
insert into t2 (b) values (1);

insert into t1 (a) select b from t2 on duplicate key update a=default;
select * from t1;

insert into t1 (a) values (1);
insert into t1 (a) select b from t2 on duplicate key update a=default(b);
select * from t1;

drop table t1, t2;
SET sql_mode = default;
--echo End of 5.0 tests.

# Bug#29906966: Failed assertion when trying to create a column with literal

--error ER_INVALID_DEFAULT
CREATE TABLE ts(ts TIMESTAMP DEFAULT TIMESTAMP'2019-10-01 01:02:03');
--error ER_INVALID_DEFAULT
CREATE TABLE dt(dt DATETIME DEFAULT TIMESTAMP'2019-10-01 01:02:03');
--error ER_INVALID_DEFAULT
CREATE TABLE ints(a INT DEFAULT TIMESTAMP'2019-10-01 01:02:03');
--error ER_INVALID_DEFAULT
CREATE TABLE t(t TIME DEFAULT TIME'01:02:03');
--error ER_INVALID_DEFAULT
CREATE TABLE d(d DATE DEFAULT DATE'2019-10-01');



--echo # Bug#33322551: hex-blob not respected in DDL during mysqldump
--echo #

# For this test, keep in mind that we have two similar-but-distinct tools,
# mysqldump and the newer mysqlpump. Both will be tested here.

--echo
--echo # Create a table with a binary default that is not valid UTF-8.
# There's no guarantee such a default is valid in a target character-set
# like UTF-8, which means that if we just print the value as part of a
# SHOW CREATE TABLE statement (of which we promised the client we'd send
# it in UTF-8), the total of the SHOW CREATE TABLE statement may be an
# invalid string. This is bad at the best of times, but really not what
# we want in a database dump, i.e. any form of backup.
CREATE TABLE t1 (f1 BINARY(6)  NOT NULL DEFAULT 0x414243FAFA00,
                 f2 VARCHAR(6) CHARACTER SET ujis DEFAULT 0xA4A2,
                 f3 BIT(4) DEFAULT b'1101');

--echo
--echo # Let's see what SHOW CREATE TABLE makes of it.
--echo # Should look like 'ABC' followed by binary garbage on unpatched server.
--echo # On a patched server, it should show the same value prefixed by its
--echo # charset ('_binary' in this case), or show a hex-value.
SHOW CREATE TABLE t1;

--echo
--echo # Show that we do not erraneously print the character set designator
--echo # ("_binary", etc.) when printing the default as a field (rather than
--echo # as part of a statement).
SELECT data_type,character_set_name,
       column_default
  FROM information_schema.columns
 WHERE table_name='t1'
   AND column_name='f1';

# This is an interesting one.
# We get a field 'column_default' with that contains the default value,
# a character that when represented in ujis has the value 0xA4A2.
# Since for our convenience, the field is then converted to the
# character-set we're actually using (UTF-8, this is confirmed by
# the third column in our select giving a UTF-8 readable character),
# just taking HEX(column_default) would give an unexpted value
# (namely, the hex-representation of the UTF-8 encoded character,
# not the hex-representation of the ujis encoded character).
# To get the hex-representation of the ujis-encoded character
# (i.e. the same hex-value as in the CREATE-statement), we must
# therefore convert the character-set *back* to ujis:
#   HEX(CONVERT(column_default USING ujis))
# Thus, the default is _ujis 0xA4A2, this is converted to utf-8
# for our "convenience", and we converted it right back. :-/
SELECT data_type,
       character_set_name,HEX(CONVERT(column_default USING ujis)),
       column_default
  FROM information_schema.columns
 WHERE table_name='t1'
   AND column_name='f2';

SELECT data_type,
       character_set_name,
       column_default
  FROM information_schema.columns
 WHERE table_name='t1'
   AND column_name='f3';


--echo
--echo # INSERT the defined DEFAULT into the table, then retrieve it.
--echo # When we hexify the result, the value should be the same as
--echo # in the original CREATE TABLE statement.
INSERT INTO t1 VALUES(DEFAULT,DEFAULT,DEFAULT);
SELECT "--base--";
SELECT HEX(f1),HEX(f2),HEX(f3) FROM t1;

--echo
--echo # mysqldump the table. In the unpatched server, this will dump a
--echo # CREATE TABLE statement with a broken default value.
--exec $MYSQL_DUMP --skip-comments test > $MYSQLTEST_VARDIR/tmp/bindfltdump.sql

--echo
--echo # Drop the table,
DROP TABLE t1;
--echo # then recreate it from the dumped file.
--exec $MYSQL --show-warnings test < $MYSQLTEST_VARDIR/tmp/bindfltdump.sql

--echo
--echo # Add another row with the DEFAULT, then retrieve both rows.
--echo # If their hex values are not the same, we broke the DEFAULT
--echo # in mysqldump (on account of SHOW CREATE TABLE printing the
--echo # DEFAULT clause wrong).
INSERT INTO t1 VALUES(DEFAULT,DEFAULT,DEFAULT);
SELECT "--base,dump--";
SELECT HEX(f1),HEX(f2),HEX(f3) FROM t1;

--echo
--echo # Now dump the table using mysqlpump.
--exec $MYSQL_PUMP --databases test > $MYSQLTEST_VARDIR/tmp/bindfltpump.sql

--echo
--echo # Drop the table,
DROP TABLE t1;
--echo # then recreate it from the pumped file.
--exec $MYSQL --show-warnings test < $MYSQLTEST_VARDIR/tmp/bindfltpump.sql

--echo
--echo # Add another row with the DEFAULT, then retrieve three rows.
--echo # If their hex values are not the same, we broke the DEFAULT
--echo # in mysqlpump (on account of SHOW CREATE TABLE printing the
--echo # DEFAULT clause wrong).
INSERT INTO t1 VALUES(DEFAULT,DEFAULT,DEFAULT);
SELECT "--base,dump,pump--";
SELECT HEX(f1),HEX(f2),HEX(f3) FROM t1;

--echo
--echo # Clean up.

DROP TABLE t1;
--remove_file $MYSQLTEST_VARDIR/tmp/bindfltdump.sql
--remove_file $MYSQLTEST_VARDIR/tmp/bindfltpump.sql