jakob
commented
5 years ago OK, this is a bug. Postico should behave as you describe, but I verified that it doesn't (on macOS 10.14.4 / Postico 1.5.6). Type select is a built-in feature of the table view / outline view, so it should theoretically work just like in Finder.
Note to self: Type select does work correctly in the main view (see screenshot).
I remember that I had some issues with type select in the past, but I can't recall the details. I'll investigate.
elahmo
In the list of tables, the current implementation jumps to the tables having name equal to the typed key.
This works fine in most cases, however in applications with a lot of tables where users might want to navigate quickly, it might be useful to not just catch a single character, but rather wait for the typing to stop, and to jump to the table matching the string.
In JS world, this is equivalent to behaviour demonstrated here: https://schier.co/blog/2014/12/08/wait-for-user-to-stop-typing-using-javascript.html
An example with the following tables:
If someone types
th, wanting to go to the table three, Postico would actually jump totwoand thenhello, since they matchtandh. The improved behaviour here would be to actually jump to tablethreeand intuitively, this might be the expected behaviour.I am aware this might be nitpicking, and there is a CMD+P shortcut, however that is rather slow compared to quick jumping. I happen to have a muscle memory for this from Finder, VSCode and I catch myself doing this dozens of times daily in Postico.
One more specific scenario is with Django framework for Python. The way its database works is by prefixing table names with app names, which can be quite extensive. So a table for
appname, would actually haveappname_logs, and this would save a lot of time in cases like this with large codebases and table counts.This is (kinda) relevant to #396 and #592.