-
Notifications
You must be signed in to change notification settings - Fork 102
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
[Bug] Getting UniqueConstraintError
when using Schema.upsert
#1047
Comments
UniqueConstraintError
when using Schema.upsert
UniqueConstraintError
when using Schema.upsert
Thanks for the bug report, this indeed looks like an edge case within Ponder. Working on a fix. Do you know if this occurred during historical or realtime indexing? |
Bump on this @benbaessler - I was able to reproduce and fix this issue in realtime, but not in historical (#1072). If you can confirm that this happened while handling a new live event (not a historical event), I'll merge that and consider this completed. |
In my deployment logs on Railway I'm getting this error when starting the application.
This is the code that caused it:
The issue came up when I redeployed the project due to an unrelated change.
The text was updated successfully, but these errors were encountered: