Skip to content
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

UnsupportedResultException with Aurora Serverless V2 #164

Open
ryanmargono opened this issue Feb 11, 2024 · 6 comments
Open

UnsupportedResultException with Aurora Serverless V2 #164

ryanmargono opened this issue Feb 11, 2024 · 6 comments

Comments

@ryanmargono
Copy link

ryanmargono commented Feb 11, 2024

I'm getting UnsupportedResultException: The result contains the unsupported data type regtype about every other request. I'm using the same postgres engine, version, and models as my Aurora Serverless V1.

Also seeing that migrations are not running with sync enabled.

Any suggestions?

@ArsenyYankovsky
Copy link
Owner

Please read the list of supported column types in the official document here. The UnsupportedResultException is thrown from the AWS SDK itself.

@ryanmargono
Copy link
Author

Hey @ArsenyYankovsky, I read through that prior to migration and I confirmed through the RDS query editor that there are no unsupported types in my schema.

Furthermore, RDS query editor (which uses Data API under the hood) works flawlessly. This leads me to believe there could be something wrong with the lib.

@vin1627
Copy link

vin1627 commented May 14, 2024

the same issue that I've encountered. Im using typeorm then connect to Data API. at first run of the database it was successfully update/ migrate my schema after that it will show the error on 2nd run and so on
image

@ficzusistvan
Copy link

Hi! I'm experiencing the same issue. I tried registering a type parser:
const registerCustomTypeParsers = () => { types.setTypeParser(2206, (val) => { console.log({ val }) return val }) // 2206 is the OID for regtype } , but with no luck. Any suggestions?

@vin1627
Copy link

vin1627 commented May 27, 2024

I've only encountered this when I used dataAPI.
I tried to use the host from RDS then I was able to avoid this error

@ficzusistvan
Copy link

Thanks @vin1627 ! Directly accessing the underlying postgres db solved the issue.
I was trying to generate/run migrations when I encountered this error.
The ugly solution for me is to use a DataSource without Data API for migrations, the problem in this case is that the db must be publicly accessible..

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

No branches or pull requests

4 participants