Below is the list of changes that have just been committed into a local
5.1 repository of istruewing. When istruewing does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html
ChangeSet@stripped, 2007-03-16 09:17:12+01:00, istruewing@stripped +1 -0
Merge istruewing@stripped:/home/bk/mysql-5.1-engines
into blade08.mysql.com:/data0/istruewing/autopush/mysql-5.1-bug25289
MERGE: 1.2409.86.1
storage/myisam/ha_myisam.cc@stripped, 2007-03-16 09:17:09+01:00, istruewing@stripped +0 -0
Auto merged
MERGE: 1.210.1.1
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: istruewing
# Host: blade08.mysql.com
# Root: /data0/istruewing/autopush/mysql-5.1-bug25289/RESYNC
--- 1.211/storage/myisam/ha_myisam.cc 2007-03-16 09:17:16 +01:00
+++ 1.212/storage/myisam/ha_myisam.cc 2007-03-16 09:17:16 +01:00
@@ -1020,6 +1020,22 @@
ha_rows rows= file->state->records;
DBUG_ENTER("ha_myisam::repair");
+ /*
+ Normally this method is entered with a properly opened table. If the
+ repair fails, it can be repeated with more elaborate options. Under
+ special circumstances it can happen that a repair fails so that it
+ closed the data file and cannot re-open it. In this case file->dfile
+ is set to -1. We must not try another repair without an open data
+ file. (Bug #25289)
+ */
+ if (file->dfile == -1)
+ {
+ sql_print_information("Retrying repair of: '%s' failed. "
+ "Please try REPAIR EXTENDED or myisamchk",
+ table->s->path.str);
+ DBUG_RETURN(HA_ADMIN_FAILED);
+ }
+
param.db_name= table->s->db.str;
param.table_name= table->alias;
param.tmpfile_createflag = O_RDWR | O_TRUNC;
| Thread |
|---|
| • bk commit into 5.1 tree (istruewing:1.2494) | ingo | 16 Mar |