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.

Sign up for GitHub

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

Jump to bottom

FIX: SQL for filter drop down didn't use the DISTINCT keyword #1684

Merged
merged 1 commit into from Jun 27, 2023
Merged

FIX: SQL for filter drop down didn't use the DISTINCT keyword #1684

merged 1 commit into from Jun 27, 2023

Conversation

JindrichSusen
Copy link
Contributor

No description provided.

@origambot
Copy link

This pull request has been mentioned on ORIGAM Community. There might be relevant details there:

https://community.origam.com/t/cant-list-values-for-a-filter-based-on-an-enumeration-column-refxxxid-on-a-field-with-uselookupvalue-set/2878/4

@washibana washibana changed the title FIX: SQL for filter drop down uses the DISTINCT keyword FIX: SQL for filter drop down didn't use the DISTINCT keyword Jun 27, 2023
@washibana washibana merged commit 0b3406e into master Jun 27, 2023
10 checks passed
@washibana washibana deleted the distinct-in-filter-values-sql branch June 27, 2023 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@washibana washibana washibana approved these changes

@tvavrda tvavrda Awaiting requested review from tvavrda tvavrda is a code owner

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@JindrichSusen @origambot @washibana