#36420: Use actual SQLite limits in last_executed_query()
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner:
Type: | myoungjinGo
Cleanup/optimization | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"c4e07f94ebc1f9eaa3dae7b3dc6a2b9832182a10" c4e07f94]:
{{{#!CommitTicketReference repository=""
revision="c4e07f94ebc1f9eaa3dae7b3dc6a2b9832182a10"
Fixed #36420 -- Used actual SQLite limits in last_executed_query()
quoting.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36420#comment:7>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a6044efb2-e50b7219-c3d3-485f-863f-519c9f034633-000000%40eu-central-1.amazonses.com.
