Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#25631 closed Bug (fixed)

AsGeoJSON, AsGML, AsKML are listed as supported by SpatiaLite without taking into account used version

Reported by: Sergey Fedoseev Owned by: nobody
Component: GIS Version: 1.9b1
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no

Description


Change History (8)

comment:2 by Tim Graham, 9 years ago

Triage Stage: Unreviewed → Ready for checkin
Version: master → 1.9b1

comment:3 by Claude Paroz, 9 years ago

I'm not sure whether we should simply remove _version_greater_2_4_0_rc4. A system with such old version of Spatialite is probably also using an unsupported version of Python (Debian squeeze is such a case for example).

comment:4 by Tim Graham, 9 years ago

Sounds good to me, Claude. I didn't lookup how old that check was.

comment:5 by Sergey Fedoseev, 9 years ago

SpatiaLite was released on 2010-01-10 and Python 2.7 was released on 2010-01-10, so I think this version mix could used in theory, however I don't think anyone will use such old software and new Django version together.
I think it would be more correct to apply the current patch to Django 1.9 and fully drop support to SpatiaLite 2.4 in the next release.

Version 0, edited 9 years ago by Sergey Fedoseev (next)

comment:6 by Tim Graham <timograham@…>, 9 years ago

Resolution: → fixed
Status: new → closed

In 6fb9424f:

[1.9.x] Fixed #25631 -- Fixed support detection for some DB functions in SpatiaLite backend.

comment:7 by Tim Graham, 9 years ago

Patch needs improvement: set
Triage Stage: Ready for checkin → Accepted

Sure, I merged that commit to 1.9.x. Could you update the PR for master?

comment:8 by Claude Paroz, 9 years ago

Note that we are not dropping support for SpatiaLite 2.4, just for pre-RC4 versions.

Note: See TracTickets for help on using tickets.
Back to Top