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

Think about argument to dbRemoveTable() that drops only if the table exists #197

Closed
krlmlr opened this issue Oct 15, 2017 · 2 comments
Closed

Comments

@krlmlr
Copy link
Member

krlmlr commented Oct 15, 2017

Useful for dbWriteTable() or for manually implementing it (#74).

Naming suggestion: dbRemoveTable(safe = TRUE)

@hadley
Copy link
Member

hadley commented Dec 4, 2017

I think the right argument is force = TRUE following the convention of rm; the default would be force = FALSE

krlmlr added a commit to r-dbi/RSQLite that referenced this issue Apr 24, 2018
- New argument `fail_if_missing` (default: `TRUE`) to `dbRemoveTable()` (r-dbi/DBI#197).
krlmlr added a commit to r-dbi/RPostgres that referenced this issue Apr 24, 2018
- New argument `fail_if_missing` (default: `TRUE`) to `dbRemoveTable()` (r-dbi/DBI#197).
krlmlr added a commit to r-dbi/RMariaDB that referenced this issue Apr 24, 2018
- New argument `fail_if_missing` (default: `TRUE`) to `dbRemoveTable()` (r-dbi/DBI#197).
@krlmlr
Copy link
Member Author

krlmlr commented Apr 24, 2018

I've decided in favor of fail_if_missing = TRUE, because --force in rm implies more than just "skip if missing".

@github-actions github-actions bot locked and limited conversation to collaborators Oct 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants