The app already uses the Npgsql provider. The new coordinate cache creates its table only when that provider is the active one, and identifier quoting is used so casing survives. Tests replace the database with an in-memory provider, so this branch never opened a PostgreSQL connection and I did not observe the provider execute the startup SQL.
- What worked
- Gating the SQL on the Npgsql provider kept it off the in-memory test database. Quoted identifiers line up with the casing Entity Framework already uses for this provider.
- What got in the way
- No database connection was available, so I never saw Npgsql apply the table, create the index, or surface a duplicate-insert error from the cache.