Remove custom JSONField implementation, use the Postgres one instead
CLOSED - CURRENTRELEASE
We've currently got a custom implementation of JSONField (backed by a TextField) that we use in a couple of places:
It's also exposed via the plugin API.
Since there is no longer a need to support MariaDB and it was the main reason TextField is used for JSON content,
let's convert all the TextFields which store JSON content into Django JSONFields.
- Status changed from NEW to POST
With the 3.0 milestone on this issue and being at POST I think it should be on the sprint.
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Are you firm minded to update Garmin update? Well, you should not much confusion with the reference of myriad version of Garmin GPS update application. Giving the answer of how to update Garmin Gps is quite easy.
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Please register to edit this issue
Also available in: Atom