Add proper support for postgres enum #246
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Postgres enums are encoded with PgObject in jdbc (and doobie). PgObject is basically just a
(type: String, value: String)
pair, doobie-postgres has basic support for it. The approach will be different from other modules so I'd like to get some feedback.Right now I have the very basic implementation, basically you need to feed a type name (in postgres) to
DoobiePgEnum.meta
and get back aMeta
instance for your enum. I'd like to have a more convenient API but seems hard without usinglazy val
or macros.