-
Arnab Ray authored
Problem: -------- The --print-log option of ndb_restore does not produce valid SQL statements. Fix: ---- Introduced a new option --print-sql-log which produces usable SQL statements. This option has the following constraints: 1. All the tables being restored must have explicitly defined primary keys. This is due to the fact that queries fired on tables with 'hidden' primary keys are logged in a manner such that they cannot be converted to valid SQL 2. Only one of the --print-sql-log and --print-log options can be passed as parameters during a restore 3. The tables being restored must not have columns of type blob
Arnab Ray authoredProblem: -------- The --print-log option of ndb_restore does not produce valid SQL statements. Fix: ---- Introduced a new option --print-sql-log which produces usable SQL statements. This option has the following constraints: 1. All the tables being restored must have explicitly defined primary keys. This is due to the fact that queries fired on tables with 'hidden' primary keys are logged in a manner such that they cannot be converted to valid SQL 2. Only one of the --print-sql-log and --print-log options can be passed as parameters during a restore 3. The tables being restored must not have columns of type blob
Loading