[MDEV-32504] Search by I_S.KEY_PERIOD_USAGE.CONSTRAINT_NAME does not work Created: 2023-10-17  Updated: 2024-01-01  Resolved: 2024-01-01

Status: Closed
Project: MariaDB Server
Component/s: Information Schema
Affects Version/s: N/A
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Nikita Malyavin
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-32503 Queries from I_S.KEY_PERIOD_USAGE do ... In Testing
Problem/Incident
is caused by MDEV-22597 Add views for periods in information_... In Testing

 Description   

--source include/have_innodb.inc
 
create table t (a int, b date, c date, period for app(b,c), unique idx(a, app without overlaps));
 
select table_name, constraint_name from information_schema.key_period_usage where table_name = 't';
select table_name, constraint_name from information_schema.key_period_usage where constraint_name = 'idx';
 
# Cleanup
drop table t;

bb-11.3-periods-schema 24018c74fae6e5a93b93c2efefd60bde4ad1488e

select table_name, constraint_name from information_schema.key_period_usage where table_name = 't';
table_name	constraint_name
t	idx
select table_name, constraint_name from information_schema.key_period_usage where constraint_name = 'idx';
table_name	constraint_name
drop table t;



 Comments   
Comment by Nikita Malyavin [ 2024-01-01 ]

Same problem as MDEV-32503

Generated at Thu Feb 08 10:31:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.