I guess there's nothing Django could do except perhaps throw a more helpful error message. Feel free to submit a ticket and/or patch if you see any value in that and if it seems feasible. I'm not sure about that offhand.
On Monday, December 12, 2016 at 8:57:09 PM UTC-5, Francis Fisher wrote: > > So it turns out that a different user owned the non-managed tables, which > seemed to prevent the django user from accessing certain information about > those tables. > -- You received this message because you are subscribed to the Google Groups "Django users" 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]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5aa3783f-ef00-40be-9b80-d4bc40691620%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
