Thijs
Thijs
As this relies on parquet files that aren't provided, this is not a reproducable example I'd be happy to debug it, but it first has to be reproducable
I suspect this is a DBeaver issue, no? This might be the source, but that's entirely speculating
That issue is more relevant here: https://github.com/duckdb/duckdb-mysql If it doesnt already exist there
I don't exactly follow, I guess you're talking about nested namespaces which we don't currently support? I'm not sure how that relates to authorization and security, that lies in the...
Hmm okay I understand now, but that doesn't sound like it should be DuckDB's responsibility. This sounds like the S3 credentials created should have their scope limited to that namespace,...
https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-resource-based-policies.html
I imagine `||` uses default null behavior of "null in, null out", which is causing this to return NULL because one of the input sides is null
> Well, even `||` is inconsistent: > > ``` > >>> duckdb.sql("select a || a from (select cast(null as int32[]) as a)") > ┌──────────┐ > │ (a || a) │...
> There's also this strange behavior where giving `null` a type changes the behavior of the function entirely: > > ``` > >>> duckdb.sql("select list_concat(cast(null as int32[]), cast(null as int32[]))...
Hmm interesting, I'm not aware of any major changes we made that might affect this