pingcap/tidb

Do not allow br full restore if table structure exists

Open

#32.615 aperta il 24 feb 2022

Vedi su GitHub
 (2 commenti) (0 reazioni) (0 assegnatari)Go (6186 fork)batch import
component/brhelp wantedtype/feature-request

Metriche repository

Star
 (40.090 star)
Metriche merge PR
 (Merge medio 14g 4h) (346 PR mergiate in 30 g)

Descrizione

Feature Request

Is your feature request related to a problem? Please describe:

Currently, when trying to br restore a table after run query "delete from t1;" and "truncate table t1;" is different:

CREATE TABLE `t1` (`a` int(11) NOT NULL,  PRIMARY KEY (`a`));
insert into t1 values (1), (2);
br backup t1;
delete from t1;
restore t1 => BR:Restore:ErrRestoreChecksumMismatch
CREATE TABLE `t1` (`a` int(11) NOT NULL,  PRIMARY KEY (`a`));
insert into t1 values (1), (2);
br backup t1;
truncate table t1;
restore t1 => Success

Describe the feature you'd like:

After execute query "delete from t1;" or "truncate table t1; br restore should not allow user to restore to the table t1, as table structure still exists in this cases.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

Guida contributor