Skip to content

Conversation

@megies
Copy link

@megies megies commented Apr 29, 2016

By enumerating index field and adding it to the unique key.

This fixes a problem I have in a project depending on django-plugins. Not sure if this is the right way to fix this or if the index field is used otherwise in different spots. I didn't see it in use in any case.. @krischer?

megies added a commit to krischer/jane that referenced this pull request May 9, 2016
@megies megies force-pushed the fix_multiple_plugins_same_name branch from 0fdd130 to 31ae955 Compare May 9, 2017 10:37
@megies
Copy link
Author

megies commented May 9, 2017

Rebased and force-pushed (previous PR tip was 0fdd130). Also adding this change to initial migrations.

megies added a commit to megies/jane that referenced this pull request Sep 26, 2017
so existing installations can be updated properly
@megies megies force-pushed the fix_multiple_plugins_same_name branch from b6b7d0c to 19f631f Compare January 31, 2020 13:29
was getting error messages about duplicate keys, looks like the id
counter is automatically incremented as a uniq field but that index
field might not be as a plain integer field (not handled by postgres at
all?)
@megies megies force-pushed the fix_multiple_plugins_same_name branch from cdcdf46 to f38b6c6 Compare January 31, 2020 13:54
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.

1 participant