Skip to content

Transactional decorator not working after dataSource re-initialized #51

@ehdgus094

Description

@ehdgus094

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions