fix(pg): handle pg engine lowercase typeName #117
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Apr 7, 2022
|
@jeremydaly any chance you'd be okay with me rebasing this onto main so we can get it in? i'm currently having to write custom logic to resolve generated date strings into date objects and i'd rather have the driver do it as expected. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
aurora serverless with postgresql returns
typeNameas lowercase. because of this, the functionformatRecordValuedoes not function properly for pg responses.to fix, I cast the
typeNameto uppercase at the start of the function, storing it in a new conststandardizedTypeName.added a test case to cover this issue.