Skip to content

Conversation

@JostCrow
Copy link
Contributor

Because I use the filtered queryset for some other issues as well. It would be nice if the distinct could be disabled. By default, the distinct will be active so running users will not encounter an error or different results if they update.

@coveralls
Copy link

coveralls commented Aug 18, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 075a91c on JostCrow:distinct_as_setting into 1a6ea28 on miki725:master.

@JostCrow JostCrow closed this Apr 7, 2023
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.

2 participants