Allow 'Database Router' to override default `connection`

rockisch · June 23, 2025, 5:35pm

Just as an update, we recently deployed the approach I mentioned before in production, and it has been working fine for our use cases. Here’s a gist showing what we are doing:

gist.github.com

https://gist.github.com/rockisch/96425b6aaa406dcf4fb86df92715fe1e

db_override.py

# Make sure 'setup_db_override()' is called on initialization, like in 'settings.py'

# Usage:
# with db_override("replica"):
#.    x = Model.objects.all()
#     with connection.cursor() as cursor:
#.        cursor.execute("...")

import contextvars
from contextlib import contextmanager

This file has been truncated. show original

I still believe this should be treated by Django, since as @chris48s mentioned, yeah if you’re using multiple DBs for queries you’re probably using more advanced features.

I also found another post requesting a similar feature:

Topic		Replies	Views
Use DATABASE_ROUTERS to pick a database connection for Transaction API by default ORM	9	3658	April 9, 2024
Force queries in a context to execute in the named database Using the ORM	8	385	June 25, 2025
Multiple Database Switching Using the ORM	4	3522	August 29, 2023
Multiple databases in Django (is it useable?) Using Django	6	3609	September 24, 2021
we can only spcify database via using or router ? Using Django	1	514	June 16, 2020

Allow 'Database Router' to override default `connection`

Related topics