#29610: Crash in sqlite3 last_executed_query when using printf() formatting
-------------------------------------+-------------------------------------
Reporter: Matthias Kestenholz | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: invalid
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 Matthias Kestenholz):
* status: new => closed
* resolution: => invalid
Comment:
Oh wow, thanks! I'll retire this bug report. Someone else may reopen if
they think that something should be done about this.
I definitely don't think making {{{last_executed_query}}} public API by
documenting it is the right way to go. I'm using {{{str.format}}} in this
project and it simply didn't occur to me that the {{{printf}}} argument
should be escaped too (since everything worked fine as is)
--
Ticket URL: <https://code.djangoproject.com/ticket/29610#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 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/067.e026b0c9ac05d992866fea6a3c35777b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
