auto-sync: 2026-04-21 17:00:01
This commit is contained in:
@@ -45,8 +45,8 @@ CREATE TABLE IF NOT EXISTS fr24_ext.flight_tracks_fa (
|
||||
ident_icao VARCHAR(10),
|
||||
registration VARCHAR(15),
|
||||
aircraft_type VARCHAR(10),
|
||||
origin_icao VARCHAR(5),
|
||||
destination_icao VARCHAR(5),
|
||||
origin_icao VARCHAR(20),
|
||||
destination_icao VARCHAR(20),
|
||||
actual_off TIMESTAMPTZ,
|
||||
actual_on TIMESTAMPTZ,
|
||||
departure_delay INTEGER, -- seconds
|
||||
|
||||
9
tasks/flightradar24/db/migrations/006_fix_fa_varchar.sql
Normal file
9
tasks/flightradar24/db/migrations/006_fix_fa_varchar.sql
Normal file
@@ -0,0 +1,9 @@
|
||||
-- Migration: widen origin_icao / destination_icao in flight_tracks_fa
|
||||
-- Reason: FA API sometimes returns coordinates (e.g. 'L 55.61740 39.72253')
|
||||
-- instead of ICAO codes; VARCHAR(5) is too short for such values.
|
||||
-- fa_worker.py now filters these out via _icao_or_none(), but this migration
|
||||
-- prevents errors on any already-stored bad data and makes the column resilient.
|
||||
|
||||
ALTER TABLE fr24_ext.flight_tracks_fa
|
||||
ALTER COLUMN origin_icao TYPE VARCHAR(20),
|
||||
ALTER COLUMN destination_icao TYPE VARCHAR(20);
|
||||
Reference in New Issue
Block a user