-
Notifications
You must be signed in to change notification settings - Fork 185
Add support to decode enums and other types as String
#454
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
Conversation
If there is no immediately suitable codec can be found and the request is to decode as a String, then fallback to using the VARCHAR codec. [pgjdbc#429]
Automatically register an EnumStringCodec and an EnumStringArrayCodec for enums. [pgjdbc#429]
It would be great if this could be back ported to 0.8.x as well |
String
Thanks for your pull request. I'm going to generalize decoder support to fall back onto a codec that simply decodes the payload when no other codec was found. That simplifies the arrangement because it doesn't require any application configuration regarding enum codecs. |
Refactor enum to string codecs into StringDecoder and StringArrayDecoder as fallback codecs if no other codec could be found. Allow reuse of ArrayCodec. [#454][resolves #454] Signed-off-by: Mark Paluch <[email protected]>
Thank you for your contribution. That's merged, polished, and backported now. |
Refactor enum to string codecs into StringDecoder and StringArrayDecoder as fallback codecs if no other codec could be found. Allow reuse of ArrayCodec. [#429][resolves #454] Signed-off-by: Mark Paluch <[email protected]>
Refactor enum to string codecs into StringDecoder and StringArrayDecoder as fallback codecs if no other codec could be found. Allow reuse of ArrayCodec. [#429][resolves #454] Signed-off-by: Mark Paluch <[email protected]>
Make sure that:
Issue description
Fixes (or at least makes progress towards) #429