#35163: sqlite3.OperationalError: no such column: django_migrations.id
-------------------------------------+-------------------------------------
Reporter: milahu | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: sqlite | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => worksforme
Comment:
Implicit `id` is added automatically to all models. I don't think you've
explained the issue in enough detail to confirm a bug in Django. Please
reopen the ticket if you can debug your issue and provide details about
why and where Django is at fault. If you're having trouble understanding
how Django works, see TicketClosingReasons/UseSupportChannels for ways to
get help.
--
Ticket URL: <https://code.djangoproject.com/ticket/35163#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d70248b42-2bf57268-315a-4459-8262-4da670e5fcf6-000000%40eu-central-1.amazonses.com.
