#24000: create_default_site 'db' kwarg should be 'using'
-------------------------------+--------------------------------------
Reporter: tkhyn | Owner: nobody
Type: Bug | Status: new
Component: contrib.sites | Version: master
Severity: Normal | Resolution:
Keywords: sites multidb | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by tkhyn):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Old description:
> Almost a non-bug as it only prevents the creation of the 'example.com'
> entry in the `django_site` table when this table does not lie in the
> default database (in case of a multi-db setup).
>
> As the post_migrate signal uses the keyword `using`, it is indeed not
> picked up by `create_default_site` which uses `db`.
New description:
Almost a non-bug as it only prevents the creation of the 'example.com'
entry in the `django_site` table when this table does not lie in the
default database (in case of a multi-db setup).
As the post_migrate signal uses the keyword `using`, it is indeed not
picked up by `create_default_site` which uses `db`.
Trivial patch attached.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/24000#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.c8182aa1f839c21832d720cb631ffdc3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
