-
Notifications
You must be signed in to change notification settings - Fork 75
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
cascade option for dbRemoveTable()
#463
Labels
Comments
Thanks. Not all databases support |
The objective would be to make it easy for the user to append |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure how to create a temporary Postgres to reprex this.
Is a cascade option for
dbRemoveTable()
worth it? I was playing around with thedm
package and wanted to clean my database of all tables. I got the below error. Then I checked for a cascade option. However the challenge was easily circumvented by dropping the child table manually first, before runningmap()
.The text was updated successfully, but these errors were encountered: