#19068: comments in a multiple database context
----------------------------------+--------------------------------------
Reporter: esimorre | Owner: nobody
Type: Bug | Status: closed
Component: contrib.comments | Version:
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by melinath):
* status: new => closed
* resolution: => needsinfo
Comment:
I wouldn't be surprised if contrib.comments had issues related to multiple
databases. But neither of the changes suggested would improve multiple
database support. _default_manager, for example, is usually the same as
.objects, unless a new default manager is being used (in which case that
should probably be used instead of .objects).
It would be great if you could gather more information and reopen this
ticket. What's the exact problem you're seeing? Are you getting any kind
of traceback?
--
Ticket URL: <https://code.djangoproject.com/ticket/19068#comment:2>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
