DuckDB and MotherDuck support #286
Open
Conversation
This file contains 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
added 8 commits
November 10, 2024 16:40
For example, each row in a "box" table format may have "|" as its first and last character. These first and last character columns should simple be ignored when yanking a header.
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.
Add full support for DuckDB and MotherDuck (cloud serverless DuckDB).
This PR is dependent upon tpope/vim-dadbod#191 which improves table output format for DuckDB and adds MotherDuck support.
I changed a few functions in dbout to use character-based string semantics instead of byte-based. This was necessary because DuckDB table output uses multi-byte characters, but it's probably the right way to do it anyway. I also generalized yanking header to work with multi-line headers as DuckDB contains both column name and data type in the header.