[MDEV-22491] Support mariadb-check and CHECK TABLE with SEQUENCE Created: 2020-05-07 Updated: 2024-01-25 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Sequences, Server, Storage Engine - Sequence |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Minor |
| Reporter: | Pramod Mahto | Assignee: | Michael Widenius |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | Compatibility | ||
| Issue Links: |
|
||||||||
| Description |
|
SEQUENCE is based on Storage engine like InnoDB or MyISAM but CHECK TABLE or mysqlcheck fail/not supported for such sequence.
|
| Comments |
| Comment by Michael Widenius [ 2020-06-03 ] |
|
Hi! The idea with mysqlcheck is executed on all tables matching the command line options. Some options, like --repair or --optimize doesn't do anything for tables from some engines and mysqlcheck will write that on the output as a note. Some examples when this happens: I think this is the right behavior and the note's are needed to inform the user what happened. In effect, a user can ignore all rows in 'note' in the Msg_type For users that wants to avoid those extra information lines, we could consider adding a new option to mysqlcheck that would suppress all 'note' messages. mysqlcheck --notes=0|1 Regards, |