Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update DELETE Statement Documentation to Include RETURNING Clause #4010

Open
2 tasks done
rustyconover opened this issue Nov 3, 2024 · 1 comment
Open
2 tasks done
Assignees

Comments

@rustyconover
Copy link

What happens?

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?

  • Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

  • Yes, I have
@szarnyasg
Copy link
Collaborator

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.

@szarnyasg szarnyasg transferred this issue from duckdb/duckdb Nov 3, 2024
@szarnyasg szarnyasg self-assigned this Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants