#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
-------------------------------------+-------------------------------------
Comment (by milahu):
to reproduce, build https://github.com/milahu/archivebox/tree/django4 with
django 4.2.9 and run
{{{
$ archivebox init
$ sqlite3 index.sqlite3 .schema
CREATE TABLE IF NOT EXISTS "django_migrations" ("app" varchar(255) NOT
NULL, "name" varchar(255) NOT NULL, "applied" datetime NOT NULL);
}}}
expected: there should be an "id" column in the "django_migrations" table
--
Ticket URL: <https://code.djangoproject.com/ticket/35163#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d70c17963-63c2372b-b549-4bbc-a184-21221ba0ceb2-000000%40eu-central-1.amazonses.com.
