Right now, we assume that SQLedge should be used for reads, and writes should be sent to to upstream Postgres.
This means the Postgres connection to SQLedge can only be passed read queries that SQLite supports. Given the connection expects to be contacting a Postgres database we should probably handle reads that SQLite can't serve by routing them back to the upstream Postgres database, instead of using the local SQLite database.
Right now, we assume that SQLedge should be used for reads, and writes should be sent to to upstream Postgres.
This means the Postgres connection to SQLedge can only be passed read queries that SQLite supports. Given the connection expects to be contacting a Postgres database we should probably handle reads that SQLite can't serve by routing them back to the upstream Postgres database, instead of using the local SQLite database.