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

UuidMixin conflicts with BaseScopedIdMixin and BaseScopedIdNameMixin #197

Closed
jace opened this issue Nov 5, 2018 · 0 comments
Closed

UuidMixin conflicts with BaseScopedIdMixin and BaseScopedIdNameMixin #197

jace opened this issue Nov 5, 2018 · 0 comments

Comments

@jace
Copy link
Member

jace commented Nov 5, 2018

The conflict derives from conflicting uses of the url_id attribute. Both mixins provide it, but one provides a column while the other provides a rendering of a UUID.

In the migration from Talkfunnel.com to HasGeek.com, we want to use both simultaneously, with the scoped numbering on the existing Talkfunnel site and UUID-based URLs on the new site. This requires using both mixins at once, so the conflict needs to be removed somehow. One proposal: move UuidMixin's url_id into another mixin. We are unlikely to be using UUID url_id since the general pattern has been to move to SUUID. However, a survey of existing code is necessary.

jace added a commit that referenced this issue Nov 5, 2018
Also drop missing suuid fix for url_name_suuid
@jace jace closed this as completed in 02a76cd Nov 5, 2018
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

No branches or pull requests

1 participant