-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Lookup tables should be maintained directly in SQLite #17
Comments
simonw
added a commit
that referenced
this issue
Jan 23, 2018
Still todo: test that this does the right thing when working with a SQLite database that already exists and already has a partially complete lookup table in it. |
Tested like this:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When evaluating
-c
we currently use a temporary table maintained in Python space:csvs-to-sqlite/csvs_to_sqlite/utils.py
Lines 74 to 84 in 24f7012
For handling larger CSV files (#16) this would work much better if it was a SQLite table that was queried and updated as we process data. This would also help make lookup tables re-usable across multiple CSVs across several runs of the command.
The text was updated successfully, but these errors were encountered: