jakob
Search performance is poor when a database has hundreds of schemas
Hi! Small feedback on this one: the slowness would be mitigated if Postico was able to better cache the schemas and tables is has already fetched.
Example: I open a new tab. On my sidebar, I see a lot of schemas loaded, so I figure I can go ahead and search them for a given table. I click the search bar, type in the name of a table... And now Postico re-fetches the contents of all schemas one by one. If I'm unlucky and the table I'm looking for is in the schemas at the end of the alphabet, then it will be very long for me to get to it and check its structure.
@tpilewicz the big problem is that each tab is completely isolated from others. This is because each tab has its own connection, and could see different tables eg. because of the current transaction state or temp tables.
It should still be possible to sync the catalog state between tabs, but it's not trivial which is why we haven't done it yet.
What I meant is not really that all tabs should share the same catalog information, although this would definitely improve the experience :)
I rather mean that it would be nice to have access to a "cached" version of the catalog while it is being fetched.
(Just an important precision: I'm using postico for accessing a redshift cluster and doing BI, that's why I'm probably less concerned than other people about transactions and the interface reflecting exactly the DB state that the current connection must see)