The schema changed to where the trails_info_id is a column in the trails table, so we need to use that new relationship to access the trails geometry data.
closes #241
other changes include:
added trail_name and regional_trail_name to the Trail query
added pointsofinterest_id__isnull to the PoiInfo search query (found that bug when testing this change)
catch ParkingLots.DoesNotExist exception (this was an edge case I found when testing this PR's change — one of the parking_lot_ids is 0 and that record doesn't exist...)
upgraded some dependencies
Notes
We need to make sure other tables haven't changed. Here's the latest diagram from @jim-z
Overview
The schema changed to where the trails_info_id is a column in the trails table, so we need to use that new relationship to access the trails geometry data.
other changes include:
trail_nameandregional_trail_nameto theTrailquerypointsofinterest_id__isnullto thePoiInfosearch query (found that bug when testing this change)ParkingLots.DoesNotExistexception (this was an edge case I found when testing this PR's change — one of the parking_lot_ids is 0 and that record doesn't exist...)Notes
We need to make sure other tables haven't changed. Here's the latest diagram from @jim-z
I opened issue #243 to do this.
Testing Instructions
testuser& password=badpassword