mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 20:42:30 +01:00
340906f46d
between 5.0 and 5.1. The problem was that in the patch for Bug#11986 it was decided to store original query in UTF8 encoding for the INFORMATION_SCHEMA. This approach however turned out to be quite difficult to implement properly. The main problem is to preserve the same IS-output after dump/restore. So, the fix is to rollback to the previous functionality, but also to fix it to support multi-character-set-queries properly. The idea is to generate INFORMATION_SCHEMA-query from the item-tree after parsing view declaration. The IS-query should: - be completely in UTF8; - not contain character set introducers. For more information, see WL4052.
44 lines
544 B
PHP
44 lines
544 B
PHP
# - Check SHOW CREATE statement;
|
|
|
|
--echo
|
|
--echo
|
|
|
|
SHOW CREATE VIEW v1|
|
|
|
|
--echo
|
|
|
|
SHOW CREATE VIEW v2|
|
|
|
|
--echo
|
|
|
|
SHOW CREATE VIEW v3|
|
|
|
|
# - Check INFORMATION_SCHEMA;
|
|
|
|
--echo
|
|
--echo
|
|
|
|
SELECT * FROM INFORMATION_SCHEMA.VIEWS WHERE table_name = 'v1'|
|
|
|
|
--echo
|
|
|
|
SELECT * FROM INFORMATION_SCHEMA.VIEWS WHERE table_name = 'v2'|
|
|
|
|
--echo
|
|
|
|
SELECT * FROM INFORMATION_SCHEMA.VIEWS WHERE table_name = 'v3'|
|
|
|
|
# - Execute the views;
|
|
|
|
--echo
|
|
--echo
|
|
|
|
SELECT COLLATION(c1), COLLATION(c2) FROM v1|
|
|
|
|
--echo
|
|
|
|
SELECT COLLATION(c1) FROM v2|
|
|
|
|
--echo
|
|
|
|
SELECT * FROM v3|
|