| Bug #14934 | Repair Table | ||
|---|---|---|---|
| Submitted: | 15 Nov 2005 3:15 | Modified: | 10 Feb 2006 5:42 | 
| Reporter: | Zung-Lin Huang | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) | 
| Version: | 4.1 | OS: | |
| Assigned to: | CPU Architecture: | Any | |
   [15 Nov 2005 3:15]
   Zung-Lin Huang        
  
 
   [9 Jan 2006 14:36]
   Aleksey Kishkin        
  changed severity to S3, as it doesn't look like feature request.
   [10 Jan 2006 5:42]
   Valeriy Kravchuk        
  Thank you for a problem report. When it is impossible to insert data - during the REPAIR TABLE statement or after its (successfull) completion? Please, specify also the table's storage engine, exact MySQL version (4.1.x) and OS used.
   [11 Feb 2006 0:00]
   Bugs System        
  No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".

