#22339: accessing m2m relation where database is not 'default' throws error
-------------------------------------+-------------------------------------
Reporter: zzart999@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version:
(models, ORM) | 1.7-beta-1
Severity: Release blocker | Resolution: invalid
Keywords: | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by anonymous):
* status: new => closed
* resolution: => invalid
Comment:
I've done some testing on clean install and the problem seems to be
elsewhere. I can confirm the relation m2m lookups work as expected. I
going to close this ticket and file another one if im able to pinpoint the
bug mode precisely. Simple reinstall from ver. 1.6.2 to 1.7 causes the
code to fall but at the moment it's not clear to me where the problem is
...
--
Ticket URL: <https://code.djangoproject.com/ticket/22339#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/076.e583eac913a5e25cfcce12156e04615c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
