Add -o/--column-order option to insert and upsert - #847
Open
ChrisJr404 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #474
insertandupsertbuild their table using the order of columns in the incoming data. This adds-o/--column-orderso you can say which columns should come first, the same waysqlite-utils transform -oalready works:You can pass it more than once. Columns you don't name keep their original order after the ones you do, and it only affects tables the command creates, so an existing table's column order is left alone. Under the hood it just passes
column_orderthrough toinsert_all(), which already supported it.Added tests covering both
insertandupsert, plus a short docs section.📚 Documentation preview 📚: https://sqlite-utils--847.org.readthedocs.build/en/847/