Bug #56262 REPAIR STATUS
| Submitted: | 25 Aug 2010 16:42 | Modified: | 21 Mar 2011 4:19 |
|---|---|---|---|
| Reporter: | Roberto Spadim (Basic Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S4 (Feature request) |
| Version: | 5.5 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | qc | ||
[25 Aug 2010 16:42]
Roberto Spadim
[25 Aug 2010 16:44]
Roberto Spadim
maybe a flag in query... REPAIR TABLE WITH_PROGRESS table_name or REPAIR TABLE /*WITH_PROGRESS*/ table_name since some tables are very small repair table don't take a lot of time... just some minutes...
[25 Aug 2010 16:45]
Valeriy Kravchuk
Thank you for the useful feature request.
[25 Aug 2010 17:27]
Shane Bester
is this a duplicate of bug #26182 ?
[25 Aug 2010 18:38]
Roberto Spadim
yes, could it be done for repair too? i don't know anythink about repair and expected rows... since query result is one row for mysql client... (maybe many for mysql server...) any idea? i think it's ok query progress, or operation progress, since it can be sending data to client, preparing query, executing... ideas?
[21 Mar 2011 4:19]
Roberto Spadim
i will close it's a duplicate of bug 26182
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.041 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.