#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 Simon Charette):
As mentioned previously by a few contributors already, **this issue
tracker is not a support channel** so you won't get answers to you
questions.
If you are trying to stitch together code to work around a known
limitation of the framework with
[https://code.djangoproject.com/ticket/32577 regards to its lack of
support for auto-generated UUID] then you are likely to run into issues
otherwise the ticket would have likely already be resolved.
--
Ticket URL: <https://code.djangoproject.com/ticket/35163#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d7512caf1-0acccc86-9f77-4d2c-a741-dd2a0ad5f995-000000%40eu-central-1.amazonses.com.
