Skip to content

Commit 4501847

Browse files
Nischal-TonthanahalNischal-Tonthanahal
committed
Bug#33148961 FAILURE TO UPGRADE FROM 5.7, INVALID UTF8 CHARACTER STRING
PROBLEM: -------- During server upgrade from 5.7 to 8.0, an invalid comment string on a FIELD or within the body of a STORED ROUTINE failed with an error message. This error provided insufficient context to locate the object containing the invalid comment string. Additionally, An invalid comment string on a TABLE, INDEX, TABLESPACE, PARTITION or SUBPARTITION caused an assertion failure when attempting to store the string in the data dictionary. This happened during CREATE/ALTER table as well. ANALYSIS: --------- Comment strings for these objects were not validated in 5.7, and were stored as-is in the FRM file. This validation function added in 8.0 throws an error during upgrade of the FRM file with the invalid comment string. It is not practical to guess the character set of an invalid comment string during 8.0 upgrade and continue without halting. Further, it is preferred to disallow invalid metadata to be stored in the data dictionary. Hence we choose to fail upgrade providing a more suitable error message. During CREATE/ALTER, when client charset differs from system charset, any string literal was converted by the parser which replaced invalid characters with '?'. However when the client charset matched, this conversion did not take place and the invalid characters were unchecked prior to attempted storage in the DD. This caused the assertion errors in case of invalid comments on TABLE, INDEX, TABLESPACE, PARTITION and SUBPARTITION. FIX: ---- If an invalid comment string is detected during CREATE, ALTER, or UPGRADE from 5.7, we throw new error messages which provide sufficient contextual information to address the failure. Change-Id: I9e0962bd04248f9353a398c6d07385148ef49dea
1 parent efcd214 commit 4501847

27 files changed

+579
-102
lines changed

‎mysql-test/r/charset.result

+2-2
Original file line numberDiff line numberDiff line change
@@ -104,10 +104,10 @@ ERROR HY000: Invalid utf8 character string: '\xF0\x9F\x90\xAC'
104104
CREATE TABLE t1(🐬 INT);
105105
ERROR HY000: Invalid utf8 character string: '\xF0\x9F\x90\xAC'
106106
CREATE TABLE t2(a INT COMMENT "🐬");
107-
ERROR HY000: Invalid utf8 character string: 'F09F90'
107+
ERROR HY000: Comment for field 'test.t2.a' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
108108
CREATE TABLE t3(a INT);
109109
CREATE VIEW v1 AS SELECT 'x' AS'🐬';
110-
ERROR HY000: Invalid utf8 character string: 'F09F90'
110+
ERROR HY000: Definition of view 'test.v1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
111111
DROP TABLE t3;
112112
PREPARE stmt FROM "SELECT 'x' AS '🐬'";
113113
EXECUTE stmt;

‎mysql-test/r/comment_column2.result

-13
Original file line numberDiff line numberDiff line change
@@ -461,16 +461,3 @@ abcdefghijabcdefghijabcdefghijabcdefghijabcdefghijabcdefghijabcdefghijabcdefghij
461461
SELECT comment,index_comment,char_length(index_comment) FROM information_schema.statistics WHERE table_name='t1';
462462
COMMENT INDEX_COMMENT char_length(index_comment)
463463
DROP TABLE t1;
464-
#
465-
# BUG#2872424 - ASSERTION `RC == TYPE_OK` FAILED.
466-
#
467-
SET character_set_client = utf8;
468-
Warnings:
469-
Warning 3719 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
470-
set names binary;
471-
CREATE TABLE t1(c1 INT COMMENT 't�est');
472-
ERROR HY000: Invalid utf8 character string: 'F76573'
473-
CREATE TABLE t1(c1 INT);
474-
ALTER TABLE t1 ADD COLUMN c2 INT COMMENT 'test􏿿';
475-
ERROR HY000: Invalid utf8 character string: 'F48FBF'
476-
DROP TABLE t1;

‎mysql-test/r/dd_upgrade_error.result

+25
Original file line numberDiff line numberDiff line change
@@ -117,6 +117,31 @@ Pattern "The schema "xyz" referenced by routine "p1" does not exist\. Please cle
117117

118118
# Cleanup.
119119

120+
# -----------------------------------------------------------------------
121+
# Bug#33148961 FAILURE TO UPGRADE FROM 5.7, INVALID UTF8 CHARACTER STRING
122+
# -----------------------------------------------------------------------
123+
124+
# Upgrade 5.7 data directory containing a table, index, column, and
125+
# stored routine, each having an invalid character string in their
126+
# comments. Also contains a stored routine with invalid character string
127+
# in the body definition.
128+
129+
# Upgrade should fail with these errors in the log.
130+
Pattern "Comment for index 'test\.t3\.idx1' contains an invalid utf8mb3 character string: '\\xBF\\xE1'\." found
131+
Pattern "Comment for field 'test\.t2\.a' contains an invalid utf8mb3 character string: '\\xBF\\xE1'\." found
132+
Pattern "Comment for table 'test\.t1' contains an invalid utf8mb3 character string: '\\xBF\\xE1'\." found
133+
Pattern "Definition of stored routine 'test\.p1' contains an invalid utf8mb3 character string: '\\xF0\\x9F\\x90'\." found
134+
135+
# Cleanup.
136+
137+
# Upgrade 5.7 data directory containing a view with invalid body
138+
# definition string.
139+
140+
# Upgrade should fail with these errors in the log.
141+
Pattern "Definition of view 'test\.v1' contains an invalid utf8mb3 character string: '\\xF0\\x9F\\x90'\." found
142+
143+
# Cleanup.
144+
120145
# ------------------------------------------------------------------
121146
# End-of-test cleanup.
122147
# ------------------------------------------------------------------

‎mysql-test/r/events_1.result

-15
Original file line numberDiff line numberDiff line change
@@ -218,19 +218,4 @@ DROP EVENT event_test;
218218
#
219219
# End of tests
220220
#
221-
#
222-
# Bug#2469962 - INVALID UTF-8 IN COMMENT OF AN EVENT DDL CAUSES ASSERT.
223-
#
224-
SET @orig_character_set_client = @@character_set_client;
225-
SET character_set_client = utf8;
226-
Warnings:
227-
Warning 3719 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
228-
CREATE EVENT t�est ON SCHEDULE AT NOW() ON COMPLETION NOT PRESERVE DO SELECT 1;
229-
ERROR HY000: Invalid utf8 character string: 't\xF7est'
230-
CREATE EVENT event ON SCHEDULE EVERY 1 SECOND COMMENT 'test�' DO SELECT 1;
231-
ERROR HY000: Invalid utf8 character string: 'FF'
232-
CREATE EVENT event ON SCHEDULE EVERY 1 SECOND COMMENT 'test' DO SELECT 1;
233-
ALTER EVENT event COMMENT 'test�';
234-
ERROR HY000: Invalid utf8 character string: 'FF'
235-
SET character_set_client = @orig_character_set_client;
236221
DROP DATABASE events_test;

‎mysql-test/r/invalid_comment.result

+96
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
#
2+
# Bug#33148961 FAILURE TO UPGRADE FROM 5.7, INVALID UTF8 CHARACTER STRING
3+
#
4+
# Test for invalid comment strings when creating table, field, index,
5+
# partition, subpartition, tablespace, procedure, function, event.
6+
#
7+
SET NAMES utf8mb3;
8+
Warnings:
9+
Warning 1287 'utf8mb3' is deprecated and will be removed in a future release. Please use utf8mb4 instead
10+
11+
# Test CREATE statements with invalid comments.
12+
13+
CREATE TABLE t1 (a int) COMMENT 'tab🐬';
14+
ERROR HY000: Comment for table 'test.t1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
15+
16+
CREATE TABLE t2 (a int COMMENT 'col🐬');
17+
ERROR HY000: Comment for field 'test.t2.a' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
18+
19+
CREATE TABLE t3 (a int, INDEX idx1(a) COMMENT 'idx🐬');
20+
ERROR HY000: Comment for index 'test.t3.idx1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
21+
22+
CREATE TABLE t4 (a int) PARTITION BY RANGE (a) (PARTITION p1 VALUES LESS THAN (0) COMMENT 'part🐬');
23+
ERROR HY000: Comment for partition 'test.t4.p1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
24+
25+
CREATE TABLE t5 (a int) PARTITION BY RANGE (a) SUBPARTITION BY HASH(a) SUBPARTITIONS 1 (PARTITION p1 VALUES LESS THAN (0)(SUBPARTITION sp1 COMMENT 'subpart🐬'));
26+
ERROR HY000: Comment for subpartition 'test.t5.p1.sp1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
27+
28+
CREATE VIEW v1 AS SELECT 'view🐬';
29+
ERROR HY000: Definition of view 'test.v1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
30+
31+
CREATE PROCEDURE sp1() COMMENT 'proc🐬' BEGIN END;
32+
ERROR HY000: Comment for stored routine 'test.sp1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
33+
34+
CREATE FUNCTION sf1() RETURNS INT DETERMINISTIC COMMENT 'func🐬' RETURN 0;
35+
ERROR HY000: Comment for stored routine 'test.sf1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
36+
37+
CREATE EVENT evt1 ON SCHEDULE AT CURRENT_TIMESTAMP + INTERVAL 1 HOUR COMMENT 'evt🐬' DO SELECT 0;
38+
ERROR HY000: Comment for event 'test.evt1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
39+
40+
# Test ALTER statements with invalid comments.
41+
42+
CREATE TABLE t1 (a int);
43+
44+
ALTER TABLE t1 COMMENT 'tab🐬';
45+
ERROR HY000: Comment for table 'test.t1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
46+
47+
ALTER TABLE t1 MODIFY a int COMMENT 'col🐬';
48+
ERROR HY000: Comment for field 'test.t1.a' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
49+
50+
ALTER TABLE t1 ADD b int COMMENT 'col🐬';
51+
ERROR HY000: Comment for field 'test.t1.b' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
52+
53+
ALTER TABLE t1 ADD INDEX idx1(a) COMMENT 'idx🐬';
54+
ERROR HY000: Comment for index 'test.t1.idx1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
55+
56+
ALTER TABLE t1 PARTITION BY RANGE (a) (PARTITION p1 VALUES LESS THAN (0) COMMENT 'part🐬');
57+
ERROR HY000: Comment for partition 'test.t1.p1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
58+
59+
ALTER TABLE t1 PARTITION BY RANGE (a) SUBPARTITION BY HASH(a) SUBPARTITIONS 1 (PARTITION p1 VALUES LESS THAN (0)(SUBPARTITION sp1 COMMENT 'subpart🐬'));
60+
ERROR HY000: Comment for subpartition 'test.t1.p1.sp1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
61+
62+
DROP TABLE t1;
63+
64+
CREATE VIEW v1 AS SELECT 0;
65+
ALTER VIEW v1 AS SELECT 'view🐬';
66+
ERROR HY000: Definition of view 'test.v1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
67+
DROP VIEW v1;
68+
69+
CREATE PROCEDURE sp1() BEGIN END;
70+
ALTER PROCEDURE sp1 COMMENT 'proc🐬';
71+
ERROR HY000: Comment for stored routine 'test.sp1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
72+
DROP PROCEDURE sp1;
73+
74+
CREATE FUNCTION sf1() RETURNS INT DETERMINISTIC RETURN 0;
75+
ALTER FUNCTION sf1 COMMENT 'func🐬';
76+
ERROR HY000: Comment for stored routine 'test.sf1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
77+
DROP FUNCTION sf1;
78+
79+
CREATE EVENT evt1 ON SCHEDULE AT CURRENT_TIMESTAMP + INTERVAL 1 HOUR DO SELECT 0;
80+
ALTER EVENT evt1 COMMENT 'evt🐬';
81+
ERROR HY000: Comment for event 'test.evt1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
82+
DROP EVENT evt1;
83+
84+
# Test invalid comment on TABLESPACE
85+
86+
CREATE TABLESPACE ts1 ADD DATAFILE 'df1.ibd' COMMENT 'ts🐬';
87+
ERROR HY000: Comment for tablespace 'ts1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
88+
89+
# Test invalid characters in stored routine body definition
90+
CREATE PROCEDURE p1() BEGIN /* 'SP body comment: 🐬' */ END;
91+
ERROR HY000: Definition of stored routine 'test.p1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
92+
CREATE FUNCTION f1() RETURNS INT DETERMINISTIC RETURN /* 'SF body comment: 🐬' */ 0;
93+
ERROR HY000: Definition of stored routine 'test.f1' contains an invalid utf8mb3 character string: '\xF0\x9F\x90'.
94+
95+
# Cleanup
96+
SET NAMES DEFAULT;

‎mysql-test/r/sp-error.result

+4-4
Original file line numberDiff line numberDiff line change
@@ -2872,10 +2872,10 @@ ERROR HY000: Comment for routine 'nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
28722872
ERROR HY000: Comment for routine 'nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn' is too long (max = 65535)
28732873
ERROR HY000: Comment for routine 'nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn' is too long (max = 65535)
28742874
# Case 6: Test case to validate comment string.
2875-
ERROR HY000: Invalid utf8 character string: 'F09D8C'
2876-
ERROR HY000: Invalid utf8 character string: 'F09D8C'
2877-
ERROR HY000: Invalid utf8 character string: 'F09D8C'
2878-
ERROR HY000: Invalid utf8 character string: 'F09D8C'
2875+
ERROR HY000: Comment for stored routine 'test.p2' contains an invalid utf8mb3 character string: '\xF0\x9D\x8C'.
2876+
ERROR HY000: Comment for stored routine 'test.f2' contains an invalid utf8mb3 character string: '\xF0\x9D\x8C'.
2877+
ERROR HY000: Comment for stored routine 'test.p2' contains an invalid utf8mb3 character string: '\xF0\x9D\x8C'.
2878+
ERROR HY000: Comment for stored routine 'test.f2' contains an invalid utf8mb3 character string: '\xF0\x9D\x8C'.
28792879
# Cleanup
28802880
#
28812881
# Bug #24357244: CANNOT CREATE A STORED FUNCTION IF A DATABASE IS NOT

‎mysql-test/std_data/upgrade/data_57_invalid_comment_string.zip

713 KB
Binary file not shown.

‎mysql-test/std_data/upgrade/data_57_invalid_view_def_string.zip

688 KB
Binary file not shown.

‎mysql-test/t/charset.test

+2-2
Original file line numberDiff line numberDiff line change
@@ -93,10 +93,10 @@ SELECT '🐬';
9393
CREATE TABLE 🐬(a INT);
9494
--error ER_INVALID_CHARACTER_STRING
9595
CREATE TABLE t1(🐬 INT);
96-
--error ER_INVALID_CHARACTER_STRING
96+
--error ER_COMMENT_CONTAINS_INVALID_STRING
9797
CREATE TABLE t2(a INT COMMENT "🐬");
9898
CREATE TABLE t3(a INT);
99-
--error ER_INVALID_CHARACTER_STRING
99+
--error ER_DEFINITION_CONTAINS_INVALID_STRING
100100
CREATE VIEW v1 AS SELECT 'x' AS'🐬';
101101
DROP TABLE t3;
102102
PREPARE stmt FROM "SELECT 'x' AS '🐬'";

‎mysql-test/t/comment_column2.test

-14
Original file line numberDiff line numberDiff line change
@@ -170,17 +170,3 @@ SELECT table_comment,char_length(table_comment) FROM information_schema.tables W
170170
SELECT column_comment,char_length(column_comment) FROM information_schema.columns WHERE table_name='t1';
171171
SELECT comment,index_comment,char_length(index_comment) FROM information_schema.statistics WHERE table_name='t1';
172172
DROP TABLE t1;
173-
174-
--echo #
175-
--echo # BUG#2872424 - ASSERTION `RC == TYPE_OK` FAILED.
176-
--echo #
177-
178-
SET character_set_client = utf8;
179-
set names binary;
180-
--character_set binary
181-
--error ER_INVALID_CHARACTER_STRING
182-
CREATE TABLE t1(c1 INT COMMENT 't�est');
183-
CREATE TABLE t1(c1 INT);
184-
--error ER_INVALID_CHARACTER_STRING
185-
ALTER TABLE t1 ADD COLUMN c2 INT COMMENT 'test􏿿';
186-
DROP TABLE t1;

‎mysql-test/t/dd_upgrade_error.test

+61
Original file line numberDiff line numberDiff line change
@@ -330,9 +330,70 @@ let MYSQLD_LOG= $MYSQL_TMP_DIR/server.log;
330330
--echo # Cleanup.
331331
--remove_file $MYSQL_TMP_DIR/data_57_orphan_routine.zip
332332
--force-rmdir $MYSQL_TMP_DIR/data_57_orphan_routine
333+
334+
--echo
335+
--echo # -----------------------------------------------------------------------
336+
--echo # Bug#33148961 FAILURE TO UPGRADE FROM 5.7, INVALID UTF8 CHARACTER STRING
337+
--echo # -----------------------------------------------------------------------
338+
333339
--echo
340+
--echo # Upgrade 5.7 data directory containing a table, index, column, and
341+
--echo # stored routine, each having an invalid character string in their
342+
--echo # comments. Also contains a stored routine with invalid character string
343+
--echo # in the body definition.
344+
--copy_file $MYSQLTEST_VARDIR/std_data/upgrade/data_57_invalid_comment_string.zip $MYSQL_TMP_DIR/data_57_invalid_comment_string.zip
345+
--file_exists $MYSQL_TMP_DIR/data_57_invalid_comment_string.zip
346+
--exec unzip -qo $MYSQL_TMP_DIR/data_57_invalid_comment_string.zip -d $MYSQL_TMP_DIR/data_57_invalid_comment_string
347+
--let $MYSQLD_DATADIR1= $MYSQL_TMP_DIR/data_57_invalid_comment_string/db
348+
--let $MYSQLD_LOG= $MYSQLTEST_VARDIR/log/data_57_invalid_comment_string.log
349+
--replace_result $MYSQLD MYSQLD $MYSQLD_DATADIR1 MYSQLD_DATADIR1 $MYSQLD_LOG MYSQLD_LOG
350+
--error 1
351+
--exec $MYSQLD --no-defaults $extra_args --innodb_dedicated_server=OFF --secure-file-priv="" --log-error=$MYSQLD_LOG --datadir=$MYSQLD_DATADIR1
334352

353+
--echo
354+
--echo # Upgrade should fail with these errors in the log.
355+
--let SEARCH_FILE= $MYSQLD_LOG
356+
--let SEARCH_PATTERN= Comment for index 'test\.t3\.idx1' contains an invalid utf8mb3 character string: '\\\xBF\\\xE1'\.
357+
--source include/search_pattern.inc
358+
--let SEARCH_PATTERN= Comment for field 'test\.t2\.a' contains an invalid utf8mb3 character string: '\\\xBF\\\xE1'\.
359+
--source include/search_pattern.inc
360+
--let SEARCH_PATTERN= Comment for table 'test\.t1' contains an invalid utf8mb3 character string: '\\\xBF\\\xE1'\.
361+
--source include/search_pattern.inc
362+
--let SEARCH_PATTERN= Definition of stored routine 'test\.p1' contains an invalid utf8mb3 character string: '\\\xF0\\\x9F\\\x90'\.
363+
--source include/search_pattern.inc
364+
365+
--echo
366+
--echo # Cleanup.
367+
--remove_file $MYSQL_TMP_DIR/data_57_invalid_comment_string.zip
368+
--force-rmdir $MYSQL_TMP_DIR/data_57_invalid_comment_string
335369

370+
--echo
371+
--echo # Upgrade 5.7 data directory containing a view with invalid body
372+
--echo # definition string.
373+
# Note : This is not included in above data directory since the upgrade would
374+
# fail prior to reaching the check for view body definition.
375+
--copy_file $MYSQLTEST_VARDIR/std_data/upgrade/data_57_invalid_view_def_string.zip $MYSQL_TMP_DIR/data_57_invalid_view_def_string.zip
376+
--file_exists $MYSQL_TMP_DIR/data_57_invalid_view_def_string.zip
377+
--exec unzip -qo $MYSQL_TMP_DIR/data_57_invalid_view_def_string.zip -d $MYSQL_TMP_DIR/data_57_invalid_view_def_string
378+
--let $MYSQLD_DATADIR1= $MYSQL_TMP_DIR/data_57_invalid_view_def_string/db
379+
--let $MYSQLD_LOG= $MYSQLTEST_VARDIR/log/data_57_invalid_view_def_string.log
380+
--replace_result $MYSQLD MYSQLD $MYSQLD_DATADIR1 MYSQLD_DATADIR1 $MYSQLD_LOG MYSQLD_LOG
381+
--error 1
382+
--exec $MYSQLD --no-defaults $extra_args --innodb_dedicated_server=OFF --secure-file-priv="" --log-error=$MYSQLD_LOG --datadir=$MYSQLD_DATADIR1
383+
384+
--echo
385+
--echo # Upgrade should fail with these errors in the log.
386+
--let SEARCH_FILE= $MYSQLD_LOG
387+
--let SEARCH_PATTERN= Definition of view 'test\.v1' contains an invalid utf8mb3 character string: '\\\xF0\\\x9F\\\x90'\.
388+
--source include/search_pattern.inc
389+
390+
--echo
391+
--echo # Cleanup.
392+
--remove_file $MYSQL_TMP_DIR/data_57_invalid_view_def_string.zip
393+
--force-rmdir $MYSQL_TMP_DIR/data_57_invalid_view_def_string
394+
395+
396+
--echo
336397
--echo # ------------------------------------------------------------------
337398
--echo # End-of-test cleanup.
338399
--echo # ------------------------------------------------------------------

‎mysql-test/t/events_1.test

-17
Original file line numberDiff line numberDiff line change
@@ -220,21 +220,4 @@ let $wait_condition=
220220
select count(*) = 0 from information_schema.processlist
221221
where db='events_test' and command = 'Connect' and user=current_user();
222222
--source include/wait_condition.inc
223-
224-
225-
--echo #
226-
--echo # Bug#2469962 - INVALID UTF-8 IN COMMENT OF AN EVENT DDL CAUSES ASSERT.
227-
--echo #
228-
SET @orig_character_set_client = @@character_set_client;
229-
SET character_set_client = utf8;
230-
--character_set binary
231-
--error ER_INVALID_CHARACTER_STRING
232-
CREATE EVENT t�est ON SCHEDULE AT NOW() ON COMPLETION NOT PRESERVE DO SELECT 1;
233-
--error ER_INVALID_CHARACTER_STRING
234-
CREATE EVENT event ON SCHEDULE EVERY 1 SECOND COMMENT 'test�' DO SELECT 1;
235-
CREATE EVENT event ON SCHEDULE EVERY 1 SECOND COMMENT 'test' DO SELECT 1;
236-
--error ER_INVALID_CHARACTER_STRING
237-
ALTER EVENT event COMMENT 'test�';
238-
239-
SET character_set_client = @orig_character_set_client;
240223
DROP DATABASE events_test;

0 commit comments

Comments
 (0)