Details
-
New Feature
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
Description
System-versioned tables can be recognized in information_schema by TABLES.TABLE_TYPE being SYSTEM VERSIONED. Application-time period tables, however, are indistinguishable. They present in TABLES view as BASE TABLE, and the period looks like a regular check constraint both in CHECK_CONSTRAINTS and TABLE_CONSTRAINTS. As discussed earlier on Slack, the standard defines some period-specific views, I think at least most basic ones should be added.
Attachments
Issue Links
- causes
-
MDEV-32204 Server crashes in get_schema_key_period_usage_record
-
- Closed
-
-
MDEV-32205 Server crashes in get_schema_key_period_usage_record on server without InnoDB
-
- Closed
-
-
MDEV-32501 INFORMATION_SCHEMA.KEY_PERIOD_USAGE reveals information to unprivileged user
-
- Closed
-
-
MDEV-32503 Queries from I_S.KEY_PERIOD_USAGE do not obey case-sensitivity
-
- Closed
-
-
MDEV-32504 Search by I_S.KEY_PERIOD_USAGE.CONSTRAINT_NAME does not work
-
- Closed
-
- is duplicated by
-
MDEV-29055 There is no data on PERIOD FOR in information schema
-
- Closed
-
Activity
Transition | Time In Source Status | Execution Times |
---|
|
1198d 14h 6m | 1 |
|
2d 7h 58m | 1 |
|
3d 23h 49m | 1 |
|
4d 18h 31m | 2 |
|
36d 7h 20m | 2 |
|
117d 15h 23m | 2 |
|
4d 2h 44m | 1 |