Closed unconverged closed 2 years ago
Do you know if that is a new feature in 0.5.0 or a bug? I asked it here but didn't get any response: https://github.com/duckdb/duckdb/discussions/4640
This seems to be a feature, an optimisation of some kind. DuckDB ignores any UPDATE statement for an empty table, not only erroneous. As you can see from the PR, I've updated tests that use the correct parameter order, as they reported no affected rows.
We now have failing builds. The reason is that the tests with UPDATE statements and invalid parameter values are failing. Apparently, that is because DuckDB does not execute UPDATE statements on empty tables.