WL#157: Option to show all (currently) marked as crashed tables

Option to show all (currently) marked as crashed tables

Title
Task ID	157
Queue
Version	N/A
Status
Priority	N/A
Copies to

Created by	Frank	11 Oct 2010	Done
Supervisor	N/A
Lead Architect
Architecture Review
Implementor
Code Review
QA
Documentation

High-Level Description

We'd like to have a way to retrieve the currently "marked as crashed" tables.
At the moment we're parsing the error log, but there should be an easier way of
doing this.

Parsing the log is not 100%, since the log may still contain tables already
repaired. A command ("show crashed tables") could just show the currently
crashed tables.

<comment author=SergeyP>
The general trend is to move from SHOW commands towards INFORMATION_SCHEMA
tables as those allow more control over selection (while keeping SHOW commands
as user-friendly alternatives), so we should provide this information through
INFORMATION_SCHEMA, too.

I'm not sure if we can add a "crashed" column into INFORMATION_SCHEMA.TABLES
table or we'll need to create a separate I_S table for this.

Another question is what to put in the column. is "crashed" a binary (yes/no)
attribute or we have some details for it?
</comment>

Task Dependencies

Others waiting for Task 157

Task 157 is waiting for

Graph

High-Level Specification

Low-Level Design

File Attachments

	Name	Type	Size	By	Date

User Comments

Time Estimates

Name	Hours Worked	Last Updated
Total	0

	Hrs Worked	Current	Original
Total	0	0	0

Funding and Votes

Votes: 1:

67%

Funding: 0 offers, total 0 Euro

Progress Reports

(Psergey - Sat, 23 Oct 2010, 11:26)
	High Level Description modified. --- /tmp/wklog.157.old.16363 2010-10-23 11:26:33.000000000 +0000 +++ /tmp/wklog.157.new.16363 2010-10-23 11:26:33.000000000 +0000 @@ -14,6 +14,9 @@ I'm not sure if we can add a "crashed" column into INFORMATION_SCHEMA.TABLES table or we'll need to create a separate I_S table for this. + +Another question is what to put in the column. is "crashed" a binary (yes/no) +attribute or we have some details for it? </comment>

(Psergey - Sat, 23 Oct 2010, 11:20)
	High Level Description modified. --- /tmp/wklog.157.old.16190 2010-10-23 11:20:00.000000000 +0000 +++ /tmp/wklog.157.new.16190 2010-10-23 11:20:00.000000000 +0000 @@ -6,3 +6,14 @@ repaired. A command ("show crashed tables") could just show the currently crashed tables. +<comment author=SergeyP> +The general trend is to move from SHOW commands towards INFORMATION_SCHEMA +tables as those allow more control over selection (while keeping SHOW commands +as user-friendly alternatives), so we should provide this information through +INFORMATION_SCHEMA, too. + +I'm not sure if we can add a "crashed" column into INFORMATION_SCHEMA.TABLES +table or we'll need to create a separate I_S table for this. +</comment> + +

Report Generator:

Saved Reports:

WorkLog v4.0.0
  © 2010 Sergei Golubchik and Monty Program AB
  © 2004 Andrew Sweger <yDNA@perlocity.org> and Addnorya
  © 2003 Matt Wagner <matt@mysql.com> and MySQL AB