#35387: Django's Spatialite backend throws errors with Spatialite 5.0.1
-------------------------------------+-------------------------------------
Reporter: Nikolas N | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: 5.0
layer (models, ORM) |
Severity: Normal | Keywords: spatialite
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
Spatialite 5.0.1 contains a bug which causes the `SELECT
InitSpatialMetaDataFull(1)` statement called by django's database wrapper
to fail with the error:
{{{
django.db.utils.OperationalError: error in trigger
ISO_metadata_reference_row_id_value_insert: no such column: rowid
}}}
Although this is primarily a bug in Spatialite, it is expected for Django
to be compatible with this version of Spatialite, as it is shipping in
many current distributions, and upgrading to Spatialite 5.1 is not always
straightforward.
There is a patch for this issue here:
https://github.com/django/django/pull/18083
I was told patches aren't accepted for closed tickets
(https://code.djangoproject.com/ticket/32935), so I am opening this new
ticket, as the core issue here with Django + Spatialite 5.0.1 remains
unresolved.
--
Ticket URL: <https://code.djangoproject.com/ticket/35387>
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/0107018ef10a03d4-65facf47-8a68-4572-ae88-3234e4a55aac-000000%40eu-central-1.amazonses.com.
