Skip to content

Issues: altairbow/django-db-connection-pool

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.

Sign up for GitHub

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

8 Open 36 Closed
8 Open 36 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Database Transactions Not Visible on Elastic APM When Using Connection Pooling
#67 opened Dec 19, 2024 by ashwani-builds
can not work with coverage to setup test database
#66 opened Dec 3, 2024 by foxracle
SELECT @@SQL_AUTO_IS_NULL on every reuse of a connection
#65 opened Oct 30, 2024 by hamidmg
4031, 'The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior
#64 opened Aug 28, 2024 by EllenEyes
1
What is the behaviour when set workers and threads using wSGI?
#63 opened Jul 15, 2024 by daviddelucca
1
What is the difference between this and pgbouncer / other connection pooling alternatives?
#59 opened Feb 19, 2024 by YPCrumble
2
Does not detects psycopg[binary]. Tries to install psycopg2[binary].
#58 opened Jan 26, 2024 by arnab-trameter
3
Postgis backend broken (python 3.12.1, django==5.0.1, psycopg[binary,pool]==3.1.17, sqlalchemy==2.0.25)
#57 opened Jan 16, 2024 by SkyHyve
1
ProTip! Exclude everything labeled bug with -label:bug.