LiveServerTestCase does not share connection to sqlite if using spatialite

[pegler@…]

Like the title says, if the database backend is set to 'django.contrib.gis.db.backends.spatialite' instead of 'django.db.backends.sqlite3' it doesn't properly share the connection with the new threads when using LiveServerTestCase. See: ​https://github.com/django/django/blob/82b3e6ffcb9d810cc0e3ec27d25f89ce1fd525e0/django/test/testcases.py#L1080

[Matt]

patch to also support spatialite

[Matt]

I added a patch that fixes this. I was unsure how to write a test for this. Conceivably the test could start a LiveServer and override the default database to be spatialite and then make sure that a particular view loads data from the DB correctly. This test is in core and geodjango is in contrib, so I was not sure where the test should go or if it was reasonable to require spatialite be installed in order to run the tests of django core. Please advise on what test is required for this.

[Claude Paroz]

I'm not convinced this needs testing. Thanks for your patch, I will commit something soon.

[Claude Paroz <claude@…>]

In ff0d3126afbc30ae1aab3a9d352300e59937fe5e:

Fixed #19296 -- Applied test connection sharing for spatialite

Thanks pegler at gmail.com for the report and the initial patch.

[Claude Paroz <claude@…>]

In b39b0aedbfbddf8fab0c43b92dc237caa8da375f:

[1.5.x] Fixed #19296 -- Applied test connection sharing for spatialite

Thanks pegler at gmail.com for the report and the initial patch.
Backport of ff0d3126af from master.

[Preston Holmes <preston@…>]

In 49fb402edfa3f40eb9e9345447edb85c0a8c4dac:

Fixed #19296 -- Applied test connection sharing for spatialite

Thanks pegler at gmail.com for the report and the initial patch.