Unify behavior of range/generate_series with PostgreSQL
#15935
Merged
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
With this PR, e.g., range(3, 1) no longer throws an error, but instead returns an empty result. This is opinionated, but more in line with the behavior of PostgreSQL.
|
Thanks for the PR! Unifying the behavior with Postgres seems like a good idea to me. Will have a closer look after the release. |
range/generate_seriesrange/generate_series with PostgreSQL
|
Thanks! |
Antonov548
added a commit
to Antonov548/duckdb-r
that referenced
this pull request
Feb 27, 2025
Unify behavior of `range`/`generate_series` with PostgreSQL (duckdb/duckdb#15935)
krlmlr
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Mar 5, 2025
Unify behavior of `range`/`generate_series` with PostgreSQL (duckdb/duckdb#15935)
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
May 15, 2025
Unify behavior of `range`/`generate_series` with PostgreSQL (duckdb/duckdb#15935)
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
May 15, 2025
Unify behavior of `range`/`generate_series` with PostgreSQL (duckdb/duckdb#15935)
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
May 17, 2025
Unify behavior of `range`/`generate_series` with PostgreSQL (duckdb/duckdb#15935)
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
May 18, 2025
Unify behavior of `range`/`generate_series` with PostgreSQL (duckdb/duckdb#15935)
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.
With this PR, e.g.,
SELECT * FROM range(3, 1)no longer throws an error, but returns an empty result instead. This choice is opinionated, but it is more in line with the behavior of PostgreSQL. Fixes part of issue #15483.