-
Notifications
You must be signed in to change notification settings - Fork 239
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
Second hierarchy migration fails due to index name clash #128
Comments
The bug was introduced in d040640#diff-1b9222a399a8e5870dd9f6852b9c1c27 @mceachen , we should fix this. |
@rcanand do you mind sending a PR ? |
@rselk, do you want to take a stab for this fix ? |
I'll be able to do a patch release tonight with a fix. Thanks for reporting |
(To clarify, I'll pull your branch when you've got it ready) |
pr sent for this #129 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use closure tree to create hierarchies for two models in my app. The first one succeeds, but the second one fails, due to the generated index name conflict ("anc_desc_idx" and "desc_idx") . Renaming these indices to be model specific ("tag_anc_desc_idx" and "tag_desc_idx", for instance) is a workaround.
Expected: The index name generated to include the model name to disambiguate indices across models.
The text was updated successfully, but these errors were encountered: