guillesd comments

Results 70 comments of


                                            guillesd

ORDER BY with function gets much slower when combined with LIMIT as function is evaluated for all rows

Are you sure that the filter is not pushdown in 1.4.3? I made this PR https://github.com/duckdb/duckdb/pull/19911 that precisely disables this optimization when there is a filter. Maybe it is better...

ORDER BY with function gets much slower when combined with LIMIT as function is evaluated for all rows

Hey @gsueur! I did some checks on one parquet file in remote s3 and indeed the filter + order by query with a limit is slightly slower. In my testing...

ORDER BY with function gets much slower when combined with LIMIT as function is evaluated for all rows

Definitely reproduced! Thanks!

Default values for columns cause Invalid Error

Hey! I don't get the same error as you do, actually I get quite a nice error: ```console Not implemented Error: Only literals (e.g. 42 or 'hello world') are supported...

`DuckLake` support in polars

DuckDB has a native integration with polars already. ```python duckdb.sql("SELECT ...").pl(lazy=True) ``` Not sure if this is what we want to use to make the DuckLake integration but I'd be...

`DuckLake` support in polars

Yes I see that for some operations they have a native client @cmdlineluser. And yes @rchui, we would need to be able to write to a database to make writing...

disabled_filesystems = 'LocalFileSystem' and ATTACH 'ducklake' don't work together

Thanks! We are on it

Can't use `OVERRIDE_DATA_PATH` with frozen ducklakes

So the problem here is that when we `add_data_files`, because we theoretically want the user to specify a file wherever they want, then we store absolute paths instead of relative...

Ducklake insertion race condition error: Failed to copy data: ERROR: duplicate key value violates unique constraint "ducklake_data_file_pkey"

Hi @soumitsalman can you check if indeed you are using Ducklake 0.2? DuckLake 0.3 should be the correct version to run 1.4 duckdb (I would think 0.2 should be incompatible)....

Ducklake insertion race condition error: Failed to copy data: ERROR: duplicate key value violates unique constraint "ducklake_data_file_pkey"

It is actually not the filename but the `data_file_id`, here you have an explanation of how this is generated https://ducklake.select/docs/stable/specification/tables/ducklake_data_file. This key needs to always be taken from the `next_file_id`...