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

CardinalityViolation: ON CONFLICT DO UPDATE command cannot affect row a second time #17

Closed
pcoccoli opened this issue Jul 16, 2021 · 0 comments · Fixed by #19
Closed

Comments

@pcoccoli
Copy link
Collaborator

With PostgreSQL, duplicate identity objects (which you would naturally have if your data comes from stix-shifter and is broken up into pages where each page has an identity object for the stix-shifter connector configuration hat produced it) will raise the above exception.
For identity objects, we should just ignore duplicates.

This was referenced Jul 16, 2021
@pcoccoli pcoccoli linked a pull request Jul 16, 2021 that will close this issue
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 a pull request may close this issue.

1 participant