Skip to content
New issue

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

bug for overwrite-tables option #272

Closed
recall704 opened this issue Sep 27, 2020 · 4 comments · Fixed by #399
Closed

bug for overwrite-tables option #272

recall704 opened this issue Sep 27, 2020 · 4 comments · Fixed by #399

Comments

@recall704
Copy link

recall704 commented Sep 27, 2020

i have two table in one db, name like xxx and xxx.bak, when i use --overwrite-tables for myloader, DROP TABLE IF EXISTS for xxx.bak will be ignore

@recall704
Copy link
Author

image

@recall704
Copy link
Author

recall704 commented Sep 27, 2020

if table name is xxx.bak, the value of split_file[1] will be xxx but not xxx.bak

@davidducos
Copy link
Member

The solution for this kind of issue, is to check the amount of elements in the split_file variable and concat again to get the real table name OR you could avoid using '.' (dot) in your table names. Pull request fixing it are welcome.

@davidducos
Copy link
Member

We are going to start a project which is not going to allow problematic filenames for myloader. It will be a check function on mydumper, other issue releated to this: #212

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants