-
Notifications
You must be signed in to change notification settings - Fork 2
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
Databases other than default #23
Comments
I've never really used it in a configuration with multiple databases except with the
I don't think it'd be an easy patch. May be though.
I'd say this would be the ideal solution and I think it makes sense to track other databases too. I'll have at look at this for the next release. A PR would be welcome too! |
You're right - all databases are tracked. This works. I guess it would be nice to track the database id for each query / query group - but I can usually understand the context and figure out the database from looking at routes and stack traces. |
Awesome!
I agree too. |
Hi,
I got a bunch of different databases under the
DATABASES
django config, not only the default one. I use a custom router set inDATABASE_ROUTERS
to pick what database to use - a different one might hit for each view / event.default
?Thanks!
The text was updated successfully, but these errors were encountered: