We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On recent version 0.11.1-4 myloader fails if a view/routine is present on the exported database objects.
How to reproduce:
CREATE DATABASE test; use test; CREATE TABLE t (qty INT, price INT); INSERT INTO t VALUES(3, 50); CREATE VIEW v AS SELECT qty, price, qty*price AS value FROM t; $ mydumper --database=test --outputdir /backup/ --verbose=3 $ myloader --directory=/backup/ --overwrite-tables --verbose=3 ** Message: 17:35:01.958: Step 1 completed, Databases created ** Message: 17:35:01.965: Thread 1 restoring table `test`.`t` from /backup/test.t-schema.sql ** Message: 17:35:01.965: Dropping table or view (if exists) `test`.`t` ** Message: 17:35:01.973: Thread 2 restoring table `test`.`v` from /backup/test.v-schema.sql ** Message: 17:35:01.973: Dropping table or view (if exists) `test`.`v` ** Message: 17:35:02.018: Creating table `test`.`t` from /backup/test.t-schema.sql ** Message: 17:35:02.019: Creating table `test`.`v` from /backup/test.v-schema.sql ** Message: 17:35:02.067: Step 2 completed, tables created ** Message: 17:35:02.067: Thread 3 restoring `test`.`t` part 0 of 0 from test.t.00000.sql. Progress 1 of 1 . ** Message: 17:35:02.080: Step 3 completed, load data finished ** Message: 17:35:02.080: Thread 4 ending ** Message: 17:35:02.080: Thread 1 ending ** Message: 17:35:02.080: Thread 2 ending ** Message: 17:35:02.081: Thread 3 ending ** Message: 17:35:02.081: Step 4 completed ** Message: 17:35:02.081: Import timings: ** Message: 17:35:02.081: Data | Index | Total | Table ** Message: 17:35:02.081: 0 00:00:00 | 0 00:00:00 | 0 00:00:00 | `test`.`v` ** Message: 17:35:02.082: 0 00:00:00 | 0 00:00:00 | 0 00:00:00 | `test`.`t` ** Message: 17:35:02.082: Step 5 started Killed mysql> show create table v ; +-------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Table | Create Table | +-------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | v | CREATE TABLE `v` ( `qty` int DEFAULT NULL, `price` int DEFAULT NULL, `value` int DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci | +-------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 1 row in set (0.00 sec)
RHEL7, PS 8.0.26
/bin/myloader: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=76df2b35b432ea91757f9d5e7ee5ac9d7eeba5e5, not stripped
The text was updated successfully, but these errors were encountered:
Thanks @jparruti for the clear test case, I added to my scripts to avoid future issues.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
On recent version 0.11.1-4 myloader fails if a view/routine is present on the exported database objects.
How to reproduce:
RHEL7, PS 8.0.26
/bin/myloader: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=76df2b35b432ea91757f9d5e7ee5ac9d7eeba5e5, not stripped
The text was updated successfully, but these errors were encountered: