-
Notifications
You must be signed in to change notification settings - Fork 55
Error: cannot use Connection.transaction() in a manually started transaction
#93
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
Comments
I'll take a look, thanks for reporting the issue. Could you provide a few lines of code from your app that cause the error? |
I added a test. Couldn't catch your error though, SQLALchemy kept catching me trying to start another transaction with an active session, so I couldn't get to the error thrown by asyncpg. If you can provide the code to reproduce, please add it to the test above and send a PR over. |
Okay, I will try. |
Cool, thanks. You can probably use your existing config, I just need a piece of code that runs and reproduces the error that I can run on my side. |
I tried using the pgdog again and encountered the same error again, I tried to create a minimally reproducible example but unfortunately I didn't succeed :( |
Ah, that's unfortunate. Okay, I'll keep digging, maybe I'll find something. In the meantime, could you run pgdog with |
Ok, I will try. |
Uh oh!
There was an error while loading. Please reload this page.
Hi, after #81 Pull Requests I start receive this error
InterfaceError('cannot use Connection.transaction() in a manually started transaction')
After that I temporarily stopped using your pooler, can you tell me if you have made any changes recently that could affect the logic? I need a pooler urgently but I am not sure if you fixed this problem.
pgdog.toml
The text was updated successfully, but these errors were encountered: