@mxpicture/tesla-superchargers-mate 0.1.52 → 0.1.53

package/db/migrations/20260903234743_address_clustering.sql

@@ -0,0 +1,69 @@
+-- Address clustering, promoted out of the unapplied sql/address_clustering.sql
+-- (deleted by this change; its functions are now in ../../sql/views.sql).
+--
+-- The clustering groups nearby TeslaMate addresses under one "seed" address, so
+-- a Supercharger site logged under half a dozen slightly different Nominatim
+-- addresses reads as one place. 001_baseline.sql has always carried its two
+-- real tables (pic_cluster, pic_cluster_member) and pic_cluster_map_v selects
+-- through them, but the scaffolding and every function stayed in an unapplied
+-- file -- which did not stop someone applying it to production by hand.
+-- Measured 2026-09-03: production had all six functions, both tables below and
+-- the trigger, none of them in any repository, and 52 clusters with 71 members
+-- being read by the clustered cost views. The schema was not reproducible.
+--
+-- What changes on the way in: the AFTER INSERT trigger on `addresses` does NOT
+-- come with it, and this migration drops the one production is carrying. Every
+-- TeslaMate table is read-only in this project -- no new columns, no triggers,
+-- no writes -- and that rule is exactly why the file stayed unapplied; a
+-- trigger also puts a whole clustering pass inside TeslaMate's own insert
+-- transaction. The scheduled `assign-clusters` command replaces it, which is
+-- the alternative the file itself named.
+--
+-- The functions are derived, so they live in ../../sql/views.sql with the rest
+-- of the routines, dropped and recreated around every migration run. Only the
+-- two tables are state, and only they are here.
+-- migrate:up
+-- Scratch space for a full rebuild. UNLOGGED: contents are disposable, and a
+-- crash may leave the table empty -- pic_rebuild TRUNCATEs it before every use.
+-- Permanent rather than TEMP to avoid plpgsql cached-plan invalidation when
+-- pic_rebuild is called more than once in a session.
+CREATE UNLOGGED TABLE IF NOT EXISTS pic_rebuild_work (
+  address_id INTEGER PRIMARY KEY,
+  lat DOUBLE PRECISION NOT NULL,
+  lon DOUBLE PRECISION NOT NULL
+);
+
+-- pic_rebuild drops and recreates this index around its bulk load (much faster
+-- than maintaining it row by row), so it is created here only so that a fresh
+-- database matches one that has already rebuilt once.
+CREATE INDEX IF NOT EXISTS pic_rebuild_work_gix ON pic_rebuild_work USING gist (ll_to_earth (lat, lon));
+
+-- Audit trail of rebuilds: one row per pic_rebuild() call. The only table here
+-- whose rows are worth keeping, and the reason this pair is promoted rather
+-- than dropped.
+CREATE TABLE IF NOT EXISTS pic_rebuild_log (
+  run_id BIGINT GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
+  diameter_m DOUBLE PRECISION NOT NULL,
+  address_count BIGINT NOT NULL,
+  cluster_count BIGINT NOT NULL,
+  started_at TIMESTAMPTZ NOT NULL,
+  finished_at TIMESTAMPTZ NOT NULL
+);
+
+-- The trigger this project must not own, and the function behind it. Guarded on
+-- `addresses` existing at all: the pic_* schema applies to a database whose
+-- TeslaMate half may not be created yet, and DROP TRIGGER IF EXISTS still fails
+-- when the table it names is missing.
+DO $$
+BEGIN
+  IF to_regclass('addresses') IS NOT NULL THEN
+    EXECUTE 'DROP TRIGGER IF EXISTS pic_addr_trg_after_insert_notify ON addresses';
+  END IF;
+END $$;
+
+DROP FUNCTION IF EXISTS pic_addr_trg_after_insert ();
+
+-- migrate:down
+DROP TABLE IF EXISTS pic_rebuild_log;
+
+DROP TABLE IF EXISTS pic_rebuild_work;

package/db/migrations/20260903234744_drop_fx_rates.sql

@@ -0,0 +1,36 @@
+-- Drop pic_fx_rates, the last physical trace of the retired FX cache.
+--
+-- docs/plans/2026-07-28_fx-rates-simplification-review.md replaced the
+-- write-once daily rate table and its `sync-fx-rates` command with an
+-- in-process LRU cache over the same base-EUR feed. The code went; the table
+-- did not, because it was never in a migration and sql/reset.sql drops by
+-- explicit name, so it survived both a full reset and a postgres_backup
+-- restore. Measured on production 2026-09-03: 0 rows, and 0 of the 7
+-- pic_charging_process_links rows pointing at one -- the column that recorded
+-- "which rate this cost was written with" has recorded nothing since the
+-- feature was removed.
+--
+-- The column goes first: its FK is ON DELETE SET NULL, which keeps the table
+-- alive, not the reference. Nothing reads either -- the generated types under
+-- packages/generated carry no PicFxRates, and the only PicFxRatesStore left is
+-- in a stale dist/ build output.
+-- migrate:up
+ALTER TABLE pic_charging_process_links
+DROP COLUMN IF EXISTS fx_rates_id;
+
+DROP TABLE IF EXISTS pic_fx_rates;
+
+-- migrate:down
+-- Plain CREATE, not CREATE IF NOT EXISTS: rolling this back onto a database
+-- that still has the table is a mistake worth failing on, not absorbing.
+CREATE TABLE pic_fx_rates (
+  id BIGINT GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
+  rate_date DATE NOT NULL,
+  quote_currency TEXT NOT NULL,
+  rate_to_eur NUMERIC(18, 8) NOT NULL,
+  fetched_at TIMESTAMPTZ NOT NULL DEFAULT now(),
+  UNIQUE (rate_date, quote_currency)
+);
+
+ALTER TABLE pic_charging_process_links
+ADD COLUMN IF NOT EXISTS fx_rates_id BIGINT REFERENCES pic_fx_rates (id) ON DELETE SET NULL;