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

table variable name collision #1

Open
bill-healey opened this issue Apr 9, 2019 · 0 comments
Open

table variable name collision #1

bill-healey opened this issue Apr 9, 2019 · 0 comments

Comments

@bill-healey
Copy link

table_name = table if table else Path(path).stem

You re-use the variable table when the original use is still in-scope. This causes a collision when processing multiple DBF files leading to non-sensical table names (table name for the current file is incorrectly set to a long string representing the description of the last table processed)

refringerator added a commit to refringerator/dbf-to-sqlite that referenced this issue Jun 30, 2022
variable name collision
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant