Postgres: is it possible to configure autocomplete lazy loading to begin from the default schema?

[kylemacfarlane]

Assuming you're using the default schema (usually "public"), these are all the same in postgres:

SELECT * FROM db.schema.table;
SELECT * FROM schema.table;
SELECT * FROM table;

But harlequin's autocomplete won't work with the third and shortest style until you have typed out one of the first two. This makes it feel like autocomplete is broken on startup until I trick it into populating by typing out the schema name once.

I think this is due to how it lazy loads the catalog? Is it possible to make it begin from the default schema rather than the database? Either pull it from the server on connect or take into account an explicit ?options=--search_path%3D=public in the connection URI?

[tconbeer]

Yeah, I like this idea. It'll take a code change in the Harlequin Postgres adapter to eagerly load the schema's tables if it matches the search path. It could be a little bit tricky, depending on the different forms the search path in Postgres can take, but should be fine

[tconbeer]

Released as 1.5.0