Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
N/A
-
None
Description
INFORMATION_SCHEMA.PERIODS (and at least some older I_S views, e.g. TABLES) work as expected with case-sensitive collations, but KEY_PERIOD_USAGE does not.
--source include/have_innodb.inc
|
|
create table t (a int, b date, c date, period for app(b,c), primary key(a, app without overlaps)); |
|
set names latin1 collate latin1_bin; |
|
select table_schema, table_name, period from information_schema.periods where table_schema = 'TEST'; |
select table_schema, table_name, period_name from information_schema.key_period_usage where table_schema = 'TEST'; |
|
set names latin1 collate latin1_general_cs; |
|
select table_schema, table_name, period from information_schema.periods where table_schema = 'TEST'; |
select table_schema, table_name, period_name from information_schema.key_period_usage where table_schema = 'TEST'; |
|
# Cleanup
|
drop table t; |
bb-11.3-periods-schema 24018c74fae6e5a93b93c2efefd60bde4ad1488e |
set names latin1 collate latin1_bin; |
select table_schema, table_name, period from information_schema.periods where table_schema = 'TEST'; |
table_schema table_name period
|
select table_schema, table_name, period_name from information_schema.key_period_usage where table_schema = 'TEST'; |
table_schema table_name period_name
|
test t app
|
set names latin1 collate latin1_general_cs; |
select table_schema, table_name, period from information_schema.periods where table_schema = 'TEST'; |
table_schema table_name period
|
select table_schema, table_name, period_name from information_schema.key_period_usage where table_schema = 'TEST'; |
table_schema table_name period_name
|
test t app
|
Attachments
Issue Links
- is caused by
-
MDEV-22597 Add views for periods in information_schema
- Closed
- is duplicated by
-
MDEV-32504 Search by I_S.KEY_PERIOD_USAGE.CONSTRAINT_NAME does not work
- Closed