Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Postgres enum values
See original GitHub issueIt seems that enum values when using postgres are not supported. Maybe even the Data API does not support enums in stringValue parameters (I just asked AWS about this).
Similar problem with jsonb type: https://github.com/jeremydaly/data-api-client/issues/34
Workaround:
I managed to get enums working by wrapping the value in a function (which tells typeorm to pass it as raw - so it avoids parameters)
example:
status: () => `'${Status.PENDING}'`,
// instead of
status: Status.PENDING,
What also works is casting (mentioned in the linked issue):
UPDATE property SET status=:status::property_status_enum
(enum name in schema is property_status_enum and passed query parameters: {status: 'pending'})
Casting requires you to use raw queries which kind of goes against typeorm workflow. Could this casting be implemented in this driver or somewhere else? @ArsenyYankovsky
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:28 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Would love this feature too @ArsenyYankovsky
@seawatts @davingreen I just released a driver with a fix for this (2.0.4). You also don’t have to use my fork anymore since new TypeORM 0.3.32 was released. Feel free to comment here or open a new issue if something doesn’t work.