Open RealOrangeOne opened 3 months ago
Hey is this still open and unassigned?
Yes. If you're interested in working on it, by all means do. I don't assign issues to people specifically though - anyone can work on anything.
@RealOrangeOne if this needs to be implemented, can we just add database
in the following tasks config if we are using DatabaseBackend
and set the default to default database defined in settings and then have all task related models to use the database defined in tasks config dict.
TASKS = {
"default": {
"BACKEND": "django_tasks.backends.immediate.ImmediateBackend",
"DATABASE": "name_of_the_database" i.e. "tasks_db" # if not set use the default
}
}
or are we looking for a more sophisticated solution than this option.
I think it'll need something a little more complex than this, as both the worker and migrations need to use this value. It might be that a database router is the only way to implement this, in which case there's not much to do ourselves besides ensure the correct DB is specified when needed.
It's currently not possible to specify which database backend will be used (ie the ones configured in
DATABASES
). Especially for SQLite, it's useful to separate the queue tables into a separate database.