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.
@Mytherin
Copy link
Collaborator

Mytherin commented Feb 20, 2025

Thanks for the PR! LGTM - could you rebase it to the branch v1.2-histrionicus so this can make the bug fix release?

@duckdb-draftbot duckdb-draftbot marked this pull request as draft February 20, 2025 16:27
@teaguesterling
Copy link
Contributor Author

Will close and re-open for reasons of troublesome client-side issues on my part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants