Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle 0-list maps (erroring out) and add test-case #54

Closed
wants to merge 194 commits into from
Closed

Conversation

carlopi
Copy link
Owner

@carlopi carlopi commented Dec 21, 2023

Fixes duckdb#10035

Richard Wesley and others added 30 commits April 6, 2023 13:28
Attempt to fix bogus reuse after move tidy failure.
Cleanup and better chunk reuse.
Reverse the bit ordering of the offset component to match PG sort ordering.
Add full suite of comparison tests.
Implement part extraction for TIMETZ.
Change min/max to match PG.
Invert Java offset too...
Tishj and others added 27 commits January 8, 2024 17:19
…ed, we do not want to use the original names in that case
…_from_reservoir_sampler

Remove chunk collection from reservoir sampler
PR feedback: Add tests and fix API argument.
Fix broken test from merge.
In a terminal, Ctrl+Z yields SIGTSTP, which is delivered to the
foreground process. It's default action is Stop and a
shell that supports job control takes over and adds the stopped process
into its list of suspended jobs.

In contrast to SIGSTOP, SIGTSTP can be caught or ignored. A common use
case for catching it is to restore the terminal to a state in which the
shell is usable again followed by suspension.

Almost all command line and text user interface programs support SIGTSTP
and work well in combination with shell job control.

This change is inspired by a patch posted in:

antirez/linenoise#141 (comment)

The traditional approach to catching and raising SIGTSTP in a signal
handler is detailed in:

https://man7.org/tlpi/code/online/dist/pgsjc/handling_SIGTSTP.c.html
Add tests for non-infinite values.
Fix duckdb#10074 - for materialized CTEs the final result names are not influenced by the aliases. Only the names of the CTE itself are influenced by the aliases.
[Python] Fix issue in DataFrame construction where non-deduplicated names were being used mistakenly
Fix duckdb#10141 - Correctly handle recursive and nested types that refer to other types in CREATE TYPE
Suspend duckdb shell on Ctrl+Z
…stead of reverting to the original error
Fix duckdb#10057: report correct error message when binding an aliased column fails
Allow unquoted keywords to be used in DETACH
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet