This repository was archived by the owner on Sep 11, 2025. It is now read-only.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
hey man, I had some problems while importing multiline csv-cellcontent.
Turns out sqlbuddy has some unsolved issues in this field.
This fix seems to work.
Feel free to merge!
Example:
"foo","bar","multiline line1
line2
line3"
^--- sqlbuddy normally turns this into 3 (erronous) rows. While actually it should see it as one row with 3 columns.
Sqlbuddie's export function (and excel) seems to export this kind of multiline-cell csv fine, however sqlbuddy's import breaks on this.