-
Notifications
You must be signed in to change notification settings - Fork 9
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
AfS Migration filters are too restrictive #1546
Comments
jacobtylerwalls
added a commit
to archesproject/arches
that referenced
this issue
Jan 19, 2024
With luck, we can just do something like this: |
jacobtylerwalls
added a commit
to archesproject/arches
that referenced
this issue
Jan 23, 2024
jacobtylerwalls
added a commit
to archesproject/arches
that referenced
this issue
Jan 31, 2024
jacobtylerwalls
added a commit
to archesproject/arches
that referenced
this issue
Feb 8, 2024
jacobtylerwalls
added a commit
to archesproject/arches
that referenced
this issue
Feb 27, 2024
jacobtylerwalls
added a commit
to archesproject/arches
that referenced
this issue
Apr 25, 2024
jacobtylerwalls
added a commit
to archesproject/arches
that referenced
this issue
Apr 25, 2024
jacobtylerwalls
added a commit
to archesproject/arches
that referenced
this issue
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An issue happens when deploying arches for science over an existing deployment - "duplicate key violates unique contstraint". This happens in the initial 0001 afs migration. This is strange because we call Plugin.objects.update_or_create - which should update the existing plugins rather than trying to pave them over. A cursory google suggests that the issue is likely that our filters for update_or_create are too restrictive. See the following
https://stackoverflow.com/questions/50915911/django-update-or-create-gets-duplicate-key-value-violates-unique-constraint
The text was updated successfully, but these errors were encountered: