#20968: Error creating Indexes on Syncdb
-------------------------------------+-------------------------------------
Reporter: burton449geo@… | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: GIS | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: geodjango, | Needs documentation: 0
spatialite, indexes | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by kenial):
Replying to [comment:8 claudep]:
> What about this patch?
> https://github.com/django/django/pull/3697
if InitSpatialMetaData query is executed in init_connection_state()
method, then it will check it **every time when opening a connection**. As
you know, there is no connection pooling on sqlite3 (and SpatiaLite)
backend by default. It means that every query execution will lead to
execute `PRAGMA table_info(geometry_columns);`, I think it's a sort of
redundancy. My patch updating django/contrib/gis/apps.py intended to
execute InitSpatialMetaData query when doing **migrate**:
https://github.com/django/django/pull/3695
What do you think about?
--
Ticket URL: <https://code.djangoproject.com/ticket/20968#comment:9>
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/080.23d638419959be93741ef13d0457cb17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
