Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
Performance of row event applying on no-unique key table is inferior and degrades
with growing size of the table.
This task aims at replacement of table scanning with key lookup, and such key - or a hidden "PK" - would be created
automatically. It may not be visible to the user as a part of the table def like the row id of Innodb is never exposed.
Attachments
Issue Links
- relates to
-
MDEV-21181 Automatic invisible primary key
- Open
-
MDEV-28412 Introduce sql_require_primary_key
- Open
-
MDEV-30557 Adding invisible SERIAL column primary key on slave break row base replication
- Closed
-
MDEV-19506 Remove the global sequence DICT_HDR_ROW_ID for DB_ROW_ID
- Closed
-
MDEV-24830 Write a warning to error log if Galera replicates InnoDB table with no primary key
- Closed
-
MDEV-25551 Assertion `mode_ == m_local || transaction_.is_streaming()` failed in BF abort
- Closed
-
MDEV-30430 Enabling system versioning on tables without primary key breaks replication
- Closed
- links to