Skip to content

Fix: Add getAvailableValues for enum to Postgres parser; #22

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rokmohar
Copy link

@rokmohar rokmohar commented Jul 18, 2024

This enables the Postgres parser to load available enum values for user defined types; This solves issue with filters for enum values. The error happened becuase of ilike comparison on custom data type for enum.

@rokmohar rokmohar changed the title Add getAvailableValues to Postgres parer; Add getAvailableValues to Postgres parser; Jul 19, 2024
@rokmohar rokmohar changed the title Add getAvailableValues to Postgres parser; Fix: Add getAvailableValues to Postgres parser; Jul 19, 2024
@rokmohar rokmohar changed the title Fix: Add getAvailableValues to Postgres parser; Fix: Add getAvailableValues for enum to Postgres parser; Jul 19, 2024
@rokmohar rokmohar force-pushed the fix/postgres-get-available-values branch 2 times, most recently from beae0a4 to 097ef9e Compare July 19, 2024 07:45
@rokmohar rokmohar force-pushed the fix/postgres-get-available-values branch from 097ef9e to 49e070c Compare July 19, 2024 07:47
@BlackRockSoul
Copy link

Currently missing the col.udt_name on line 139-144

And I don't know the purpose of marking it as mixed here, but it works perfectly with just string

Thanks anyway, will make a local patch for myself

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants