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

Transactional decorator not working after dataSource re-initialized #51

Open
ehdgus094 opened this issue Apr 17, 2024 · 1 comment
Open

Comments

@ehdgus094
Copy link

Thanks for the awesome library!

In AWS serverless environment, The DataSource has to be destroyed when the lambda request finishes and re-initialize on lambda warm-start in order to reduce the amount of the idle db connections.

On lambda cold-start, everything works fine because a new nest application gets initialized but, on lambda warm-start, the existing nest application is used and the transactional feature doesn't seem to work with the newly initialized DataSource.

I would like to know if there is any way to solve this problem. Thanks!

@ehdgus094
Copy link
Author

ehdgus094 commented Apr 18, 2024

I found out that the issue wasn't because of destruction and re-initialization of DataSource.
Transactional feature doesn't seem to work with TypeORM's lazy relation feature.

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

1 participant