Josh Wills

I assumed it was feature-freeze for 0.6

Hey all, I had a dbt-duckdb user who ran into this one on the 0.7.1 release and I created a simple script that can reproduce it locally for me: ```...

So I _think_ whatever is going wrong is going wrong around here: https://github.com/duckdb/duckdb/blob/master/src/storage/data_table.cpp#L1112 like, we should be trying to do the update against the data in the transaction local storage...

K so I'm thinking that fixing this will require updating the `Update` method above to work more like the `Delete` method here: https://github.com/duckdb/duckdb/blob/master/src/storage/data_table.cpp#L966 We will need to iterate through the...

Alright perfect, thank you so much! As it so happens I found a good workaround for this use case (instead of doing the INSERT and then the UPDATE, do the...

general thought-- these changes are a bit too massive for me to drink in all at once. Breaking them up into a series of commits-- core first, then avro/mongo/thrift, then...

I added that recently; it should be in anything after dbt-duckdb 1.7.4 and DuckDB 0.10.1 (when all of the COMMENT ON support dbt needed was added)

Hey @QishunX! Have you checked out DuckDB's bult-in glob utilities for files? https://duckdb.org/docs/data/multiple_files/overview.html That would be my recommendation here, but if that won't work for some reason, let me know...

You need to use both the "database" and the "schema" properties-- I'm assuming what you want is: ``` - name: attached_source database: attached_database schema: main ```

(If that doesn't work-- i.e., it does not then compile to "attached_database.main.attached_table", it's likely a bug)