Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
a90f34ab
Commit
a90f34ab
authored
Mar 23, 2004
by
hf@deer.(none)
Browse files
Options
Browse Files
Download
Plain Diff
Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-4.1
into deer.(none):/home/hf/work/mysql-4.1.3067
parents
15cc92ca
1f709b19
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
31 additions
and
3 deletions
+31
-3
myisam/mi_check.c
myisam/mi_check.c
+4
-3
mysql-test/r/repair_part1.result
mysql-test/r/repair_part1.result
+15
-0
mysql-test/t/repair_part1.test
mysql-test/t/repair_part1.test
+12
-0
No files found.
myisam/mi_check.c
View file @
a90f34ab
...
@@ -1274,9 +1274,10 @@ int mi_repair(MI_CHECK *param, register MI_INFO *info,
...
@@ -1274,9 +1274,10 @@ int mi_repair(MI_CHECK *param, register MI_INFO *info,
I think mi_repair and mi_repair_by_sort should do the same
I think mi_repair and mi_repair_by_sort should do the same
(according, e.g. to ha_myisam::repair), but as mi_repair doesn't
(according, e.g. to ha_myisam::repair), but as mi_repair doesn't
touch key_map it cannot be used to T_CREATE_MISSING_KEYS.
touch key_map it cannot be used to T_CREATE_MISSING_KEYS.
That is what the next line is for
... (serg)
That is what the next line is for
*/
*/
if
(
param
->
testflag
&
T_CREATE_MISSING_KEYS
)
share
->
state
.
key_map
=
((((
ulonglong
)
1L
<<
share
->
base
.
keys
)
-
1
)
&
share
->
state
.
key_map
=
((((
ulonglong
)
1L
<<
share
->
base
.
keys
)
-
1
)
&
param
->
keys_in_use
);
param
->
keys_in_use
);
...
...
mysql-test/r/repair_part1.result
View file @
a90f34ab
...
@@ -9,6 +9,21 @@ repair table t1 use_frm;
...
@@ -9,6 +9,21 @@ repair table t1 use_frm;
Table Op Msg_type Msg_text
Table Op Msg_type Msg_text
test.t1 repair error The storage engine for the table doesn't support repair
test.t1 repair error The storage engine for the table doesn't support repair
drop table t1;
drop table t1;
create table t1(id int PRIMARY KEY, st varchar(10), KEY st_key(st));
insert into t1 values(1, "One");
alter table t1 disable keys;
show keys from t1;
Table Non_unique Key_name Seq_in_index Column_name Collation Cardinality Sub_part Packed Null Index_type Comment
t1 0 PRIMARY 1 id A 1 NULL NULL BTREE
t1 1 st_key 1 st A NULL NULL NULL YES BTREE disabled
repair table t1 extended;
Table Op Msg_type Msg_text
test.t1 repair status OK
show keys from t1;
Table Non_unique Key_name Seq_in_index Column_name Collation Cardinality Sub_part Packed Null Index_type Comment
t1 0 PRIMARY 1 id A 1 NULL NULL BTREE
t1 1 st_key 1 st A NULL NULL NULL YES BTREE disabled
drop table t1;
repair table t1 use_frm;
repair table t1 use_frm;
Table Op Msg_type Msg_text
Table Op Msg_type Msg_text
test.t1 repair error Table 'test.t1' doesn't exist
test.t1 repair error Table 'test.t1' doesn't exist
...
...
mysql-test/t/repair_part1.test
View file @
a90f34ab
...
@@ -12,6 +12,18 @@ alter table t1 ENGINE=HEAP;
...
@@ -12,6 +12,18 @@ alter table t1 ENGINE=HEAP;
repair
table
t1
use_frm
;
repair
table
t1
use_frm
;
drop
table
t1
;
drop
table
t1
;
#
# disabled keys during repair
#
create
table
t1
(
id
int
PRIMARY
KEY
,
st
varchar
(
10
),
KEY
st_key
(
st
));
insert
into
t1
values
(
1
,
"One"
);
alter
table
t1
disable
keys
;
show
keys
from
t1
;
repair
table
t1
extended
;
show
keys
from
t1
;
drop
table
t1
;
# non-existent table
# non-existent table
repair
table
t1
use_frm
;
repair
table
t1
use_frm
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment