#24064: Spatialite tests could use or create real database
-------------------------------------+-------------------------------------
Reporter: coldmind | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):
* stage: Unreviewed => Accepted
Comment:
Basically, the problem is the `type` field of the
`SpatialiteGeometryColumns` model depends on the Spatialite version. And
as this happens at import time, the test machinery has not yet done its
job.
See
https://github.com/django/django/blob/51890ce8898f821d28f2f6fb6071c936e9bd88f0/django/contrib/gis/db/backends/spatialite/models.py#L16-L19
It's not the only location in Django where we could take advantage of a
lazy model field instanciation, but I'm not aware of any such method
currently. Ideas?
--
Ticket URL: <https://code.djangoproject.com/ticket/24064#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.436860942463e867a12c82ff08144b1f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
