#32935: Test suite fails with sqlite 3.36 and spatialite 5.
-----------------------------+--------------------------------------
Reporter: David Smith | Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: 3.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Comment (by Nikolas N):
I am updating a project to Django 4.2 and I'm having trouble adding this
workaround to github actions,
can someone please advise? My pull request is here:
https://github.com/ccnmtl/footprints/pull/2976
Specifically, I've added this step in my github actions script:
{{{
# https://code.djangoproject.com/ticket/32935
- name: Spatialite 5 django workaround
run: ./manage.py shell -c "import
django;django.db.connection.cursor().execute('SELECT
InitSpatialMetaData(1);')";
}}}
Which fails with the error:
{{{
django.db.utils.OperationalError: connection is bad: No such file or
directory
Is the server running locally and accepting connections on that
socket?
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32935#comment:14>
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/0107018eec719536-969490b6-d736-424d-9564-8ef4f97e7918-000000%40eu-central-1.amazonses.com.
