It looks like the source of this error is related to a spatialite internal
connection leak (discussed in this
post: https://groups.google.com/forum/#!topic/spatialite-users/xrV7CA_GlwM)
Each time Django requests a connection to the database sqlite loads the
spatialite extension module, which cr
> Fred Stluka -- mailt...@bristle.com --
> http://bristle.com/~fred/
> Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
> Open Source: Without walls and fences, we need no Windows or Gates.
> --
>
> On 1/17/17 3:59 PM, Michael Gru
> Fred Stluka -- mailt...@bristle.com --
> http://bristle.com/~fred/
> Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
> Open Source: Without walls and fences, we need no Windows or Gates.
> --
>
> On 1/17
When Django closes a database connection at the end of a request/response
cycle does that connection still maintain its hold on the database?
I ask because I am running an app on a spatialite (v4.3.0a) database,
which, due to a limitation in the GEOS library (v3.6.1-CAPI-1.10.1 r0), can
onl
4 matches
Mail list logo