#29350: Sqlite3 Introspection (get_primary_key_column) Always Returns None
-------------------------------------+-------------------------------------
Reporter: Zackary Troop | Owner: Zackary
| Troop
Type: Bug | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: sqlite3 | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by GitHub <noreply@…>):
In [changeset:"7ac3008fe473f8015bda9789be23657d3b329e6d" 7ac3008]:
{{{
#!CommitTicketReference repository=""
revision="7ac3008fe473f8015bda9789be23657d3b329e6d"
Refs #29350 -- Fixed 'invalid escape sequence' warning in SQLite
introspection.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29350#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 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.3e751f6ce7f5defdb2badbc6c6541996%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
