Mark

Results 28 issues of Mark

There are still a few places where collations have to be properly handled where they are currently not considered: * DISTINCT aggregates * LIKE/REGEX queries (this is not really possible...

reproduced

See https://github.com/duckdb/postgres_scanner/pull/217

This PR adds support for starting read-only transactions using the following syntax (also supported by Postgres): ```sql BEGIN TRANSACTION READ ONLY; ``` Standard transactions in DuckDB start out as read-only,...

Draft

Fixes #12225 This PR reverts `OVERWRITE_OR_IGNORE` to the previous behavior where files are overwritten if they exist, or ignored (left alone) if they do not. The new behavior introduced in...

(Hopefully) includes a work-around for the broken github actions Windows runners (see https://github.com/actions/runner-images/issues/10004)

Follow-up fix from https://github.com/duckdb/duckdb/pull/11470 Fixes an issue where large bulk deletes were triggering large WAL writes because the system would incorrectly assume the WAL writes would be small

We should add support for more list types (e.g. floating point lists, etc).

good first issue

* This allows us to insert into tables by defining a custom insert operator * This makes schemas work natively without needing the current work-around

long-term

This mode is a (very long tail) mode that improves compatibility between DuckDB's SQL dialect and Postgres' SQL dialect. e.g.: * `SELECT COUNT(*) FROM tbl` returns a column named `count`,...

long-term

CC @taniabogatsch Follow-up fix from https://github.com/duckdb/duckdb/pull/13372, similar to https://github.com/duckdb/duckdb/pull/13577 We could make this work by inserting into the indexes in `WriteAheadLogDeserializer::ReplayRowGroupData` - but for now we just disable this if...