#24525: AssertionError at `Query.change_aliases`
-------------------------------------+-------------------------------------
Reporter: coolRR | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jarshwah):
It's not likely that just seeing the problem is going to be enough to
reproduce on my own. I sympathise with your situation, but you're trying
to avoid billing your client by palming the work off for free to open
source contributors. We're not tier 3 support. You should (IMO) be billing
for bug fixes in situations like this.
I'm happy to meet you half way. If you can put a test case together then
we can work on fixing the issue.
Cheers
--
Ticket URL: <https://code.djangoproject.com/ticket/24525#comment:9>
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/064.efec0ba335c9f2dd07325f97e9879b72%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
