-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
importccl: support DROP TABLE [IF EXISTS] for PGDUMP #53112
Labels
A-disaster-recovery
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Comments
Hi @otan, I've guessed the C-ategory of your issue and suitably labeled it. Please re-label if inaccurate. While you're here, please consider adding an A- label to help keep our repository tidy. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
blathers-crl
bot
added
the
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
label
Aug 20, 2020
pgdump example:
ogr2ogr example:
|
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-disaster-recovery
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
A pgdump generated by default from
ogr2ogr
or usingpg_dump -clean
includes aDROP TABLE [IF EXISTS]
line that after 921c60a we no longer ignore and explicitly error out. An example of a PGDUMP i expect to work usingIMPORT PGDUMP
:Ideally we should be able to handle these -- it makes sense, especially from the geospatial perspective -- for a user to have a dump that nukes a table and overwrites it if necessary.
Might be a good start project / first issue, fwiw.
The text was updated successfully, but these errors were encountered: