Hi again, time for my next GeoDjango-on-SQLite question.
In order to load the SpatiaLite extensions for SQLite, you first need
to enable SQLite extensions in the first place. Unfortunately,
pysqlite did not expose this functionality until pysqlite 2.5.0, which
means it didn't make it into
[EMAIL PROTECTED] wrote:
> Matthew, would you mind sticking the script you used to test this up
> on dpaste?
I'd love to, but it wasn't really a script per se, so much as a hodge-
podge that involved twiddling the server, restarting it, running some
tests, changing the server config again,
On Nov 16, 11:03 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> I know this is a horribly nebulous question (like all benchmarking),
> and it's completely dependent on the speed of your machine and a
> million other factors. However, if we are going to start adding
> signals to very
Hi all,
I've been playing with adding sqlite3 back-end support to GeoDjango,
using the SpatiaLite extension. This requires executing some magic
SQL each time you connect to the database, to enable the spatial
extensions. Ticket #6064 seems like this right way to do this, by
causing the
