-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
fix(data-api): Fixed how data api driver uses and reuses a client #6869
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like you removed the client from the AuroraDataApiDriver
but not the postgres one.
Do we need the client on the postgres driver still?
src/driver/aurora-data-api-pg/AuroraDataApiPostgresQueryRunner.ts
Outdated
Show resolved
Hide resolved
Oof, because this is the aurora stuff we don't have tests for it. Also, is there a related github issue? |
Yeah it runs a couple of statements like enabling postgres extensions. |
I have tests in the driver repository. This is a fix for a bug that was reported there as well (ArsenyYankovsky/typeorm-aurora-data-api-driver#5) |
Given we can't really test this, I think it's good to merge in. 🤷 |
…peorm#6869) Now each queryRunner will have it's own client which will allow it to handle transactions correctly.
…peorm#6869) Now each queryRunner will have it's own client which will allow it to handle transactions correctly.
…peorm#6869) Now each queryRunner will have it's own client which will allow it to handle transactions correctly.
…peorm#6869) Now each queryRunner will have it's own client which will allow it to handle transactions correctly.
@ArsenyYankovsky would have been nice to keep the transactionId inside queryRunner instead of client |
Now each queryRunner will have it's own client which will allow it to handle transactions correctly.