#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
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"30f8642f2e9f4ed64ddb09163e09c1ca073b935a" 30f8642]:
{{{
#!CommitTicketReference repository=""
revision="30f8642f2e9f4ed64ddb09163e09c1ca073b935a"
Fixed #29350 -- Fix get_primary_key_column() method in sqlite3 backend
Thanks Tim Graham and Mariusz Felisiak for the reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29350#comment:6>
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.0bd0e7ab99e3cfc6950a5d0af1e6d30d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
