Skip to content

Ignore duplicate_object error on create _Schema if not exists #3668

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

Merged
merged 1 commit into from
Mar 24, 2017

Conversation

flovilmart
Copy link
Contributor

@flovilmart flovilmart commented Mar 24, 2017

@acinader probably something that you'll like as we probably should ignore this error as well. @vitaly-t @kulshekhar what do you think? Does it make sense?

@kulshekhar
Copy link
Contributor

I don't see any harm in it but I'm not sure there's any benefit. Shouldn't checking for duplicate_table error (PostgresDuplicateRelationError) be sufficient?

@flovilmart
Copy link
Contributor Author

The failure on Travis report that error: https://travis-ci.org/ParsePlatform/parse-server/jobs/214394378#L692 which is odd

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

Successfully merging this pull request may close these issues.

4 participants