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

Question: usage with multiple databases #1

Closed
validkeys opened this issue Sep 5, 2024 · 2 comments
Closed

Question: usage with multiple databases #1

validkeys opened this issue Sep 5, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@validkeys
Copy link

Firstly, I love you for this project. It saved me from having to write it and it works great.

Question for you, my project has multiple databases and therefore multiple connections through PG. My first database connection works flawlessly, however the connection to the second database starts causing errors as the money patched PG is locked into pointing at the first database it connected to.

Any advice on how to isolate this package on a per database basis?

@romeerez romeerez added the enhancement New feature or request label Sep 15, 2024
@romeerez
Copy link
Owner

Thank you for the kind words and for making this world better by writing tests!

Any advice on how to isolate this package on a per database basis?

Never thought about it so there is no way currently. But the library is small so it shouldn't be too complex to make such a change.

@romeerez
Copy link
Owner

romeerez commented Sep 15, 2024

Ready!

v1.1.0 will track different pg clients by their different connection settings (host, port, user, db name) and will run separate transactions per each db.

romeerez added a commit that referenced this issue Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants