Changing the connection info for SQL files should not flag the query as unsaved.
Occasionally, I directly use SQL to query data. However, changing the connection for SQL files annoyingly marks the query as unsaved.
Since connection info does not persist for SQL files, marking it as dirty to denote a state change seems unnecessary.
The query should only be marked as unsaved if there is a change in the editor's content.
3
votes

This is fixed in 8.7.4