Skip to content

Conversation

teaguesterling
Copy link
Contributor

This is a proposed fix for #16333 as it seems SetColumnRendering and SetRowRendering do the same thing instead of SetRowRendering returning state.columns back to the default value.

This is a proposed fix for duckdb#16333 as it seems SetColumnRendering and SetRowRendering do the same thing instead of SetRowRendering returning state.columns back to the default value.
@teaguesterling
Copy link
Contributor Author

This replaces #16334

@Tishj
Copy link
Contributor

Tishj commented Feb 20, 2025

Thanks for the swift fix!

For future reference, you can just rebase your branch, you don't need to close and open a new PR

git rebase --onto v1.2-histrionicus main patch-2
git push -f

Afterwards on the website you can Edit at the top and target v1.2-histrionicus

@teaguesterling
Copy link
Contributor Author

Thank you! @Tishj! Very much appreciate the better approach. I didn't know how to do that off-hand but also didn't have access to a terminal with the right user account so recreating ended up faster anyways.

@Mytherin Mytherin merged commit 6cdeabe into duckdb:v1.2-histrionicus Feb 21, 2025
26 of 27 checks passed
krlmlr added a commit to duckdb/duckdb-r that referenced this pull request Mar 7, 2025
Add the suggestion to verify the nullstring as part of the cast error message (duckdb/duckdb#16336)
Update shell.cpp to fix duckdb/duckdb#16333 (duckdb/duckdb#16335)
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

Successfully merging this pull request may close these issues.

3 participants