I noticed that the documentation for the DELETE statement currently doesnβt mention that a RETURNING clause can be added to return the values of the deleted rows. Since this is such a useful feature, adding it to the documentation with a quick example would be really helpful for users.
Thanks for considering this enhancement, and for all the great work youβre doing with the docs! π
To Reproduce
create table employees(name text, age int);
insert into employees values ('Kat', 32);
delete from employees returning name, age;
delete from employees returning name, age;
βββββββββββ¬ββββββββ
β name β age β
β varchar β int32 β
βββββββββββΌββββββββ€
β Kat β 32 β
βββββββββββ΄ββββββββ
OS:
Mac OS X
DuckDB Version:
v1.1.2 f680b7d08f
DuckDB Client:
CLI
Hardware:
No response
Full Name:
Rusty Conover
Affiliation:
self
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)
Did you include all code required to reproduce the issue?
[X] Yes, I have
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
Hi @rustyconover, thanks! Indeed this is missing. I transferred this issue to the duckdb-web repository where the documentation site and will resolve it next week.
What happens?
I noticed that the documentation for the
DELETE
statement currently doesnβt mention that aRETURNING
clause can be added to return the values of the deleted rows. Since this is such a useful feature, adding it to the documentation with a quick example would be really helpful for users.Thanks for considering this enhancement, and for all the great work youβre doing with the docs! π
To Reproduce
OS:
Mac OS X
DuckDB Version:
v1.1.2 f680b7d08f
DuckDB Client:
CLI
Hardware:
No response
Full Name:
Rusty Conover
Affiliation:
self
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?