Error executing tool list_flights: no such column: f.arrivalWeatherCondition
Summary
Every tool that lists flights from the local Flighty database returns a SQLite error referencing a column that doesn't exist in my Flighty DB:
Error executing tool list_flights: no such column: f.arrivalWeatherCondition
The same error is thrown by search_flights, regardless of which filter parameters are passed.
Reproduction
Calling either tool with any arguments (or none) reproduces the error:
list_flights() → error
list_flights(upcoming_only=True) → error
list_flights(upcoming_only=True, limit=10) → error
search_flights(arrival_airport="FRA") → error
search_flights(arrival_airport="FRA", after="2026-04-30", before="2026-05-01") → error
Likely cause
Looks like a schema-version mismatch between the Flighty app's SQLite database and what the MCP server's SELECT expects. The server is selecting f.arrivalWeatherCondition, but my local Flighty DB doesn't have that column — possibly because Flighty renamed/dropped the column in a recent update, or because the column was added in a Flighty version newer than mine.
A quick fix would be to make arrivalWeatherCondition (and any other recently-changed columns) optional in the SELECT — e.g. detect column presence at startup, or wrap the read in a try/except and substitute NULL when the column is absent.
Environment
Flighty app version: Version 4.9.1 (4773)
Error executing tool list_flights: no such column: f.arrivalWeatherCondition
Summary
Every tool that lists flights from the local Flighty database returns a SQLite error referencing a column that doesn't exist in my Flighty DB:
Error executing tool list_flights: no such column: f.arrivalWeatherCondition
The same error is thrown by search_flights, regardless of which filter parameters are passed.
Reproduction
Calling either tool with any arguments (or none) reproduces the error:
list_flights() → error
list_flights(upcoming_only=True) → error
list_flights(upcoming_only=True, limit=10) → error
search_flights(arrival_airport="FRA") → error
search_flights(arrival_airport="FRA", after="2026-04-30", before="2026-05-01") → error
Likely cause
Looks like a schema-version mismatch between the Flighty app's SQLite database and what the MCP server's SELECT expects. The server is selecting f.arrivalWeatherCondition, but my local Flighty DB doesn't have that column — possibly because Flighty renamed/dropped the column in a recent update, or because the column was added in a Flighty version newer than mine.
A quick fix would be to make arrivalWeatherCondition (and any other recently-changed columns) optional in the SELECT — e.g. detect column presence at startup, or wrap the read in a try/except and substitute NULL when the column is absent.
Environment
Flighty app version: Version 4.9.1 (4773)