From ef9a68b19a450262ce7711c2dd0b4dd1651328a7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20La=C5=BEa?= Date: Thu, 5 May 2022 13:14:35 +0200 Subject: [PATCH] GE-871 upsert network_type column in update_osm_route_member (#1384) Fixes #1374 This PR fixes `update_osm_route_member()` function. Before this the column `network_type` became empty after daily-update. This PR adds `network_type` into upsert together with `rank` and `concurrency_index` columns. This bug had occurred once already and had been fixed in https://github.com/openmaptiles/openmaptiles/pull/1239 but then some columns were added and these new columns were not added into the upsert. --- layers/transportation/update_route_member.sql | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/layers/transportation/update_route_member.sql b/layers/transportation/update_route_member.sql index 3b8f5a5..3a62402 100644 --- a/layers/transportation/update_route_member.sql +++ b/layers/transportation/update_route_member.sql @@ -75,7 +75,8 @@ BEGIN WHERE rm.member IN (SELECT DISTINCT osm_id FROM transportation_name.network_changes) ON CONFLICT (id, osm_id) DO UPDATE SET concurrency_index = EXCLUDED.concurrency_index, - rank = EXCLUDED.rank; + rank = EXCLUDED.rank, + network_type = EXCLUDED.network_type; END; $$ LANGUAGE plpgsql;