3 ms·

Could be promising but falls short for my use cases, which mainly consists of running ad hoc queries. I don't like Squirrel, but here are a few things squirrel

Could be promising but falls short for my use cases, which mainly consists of running ad hoc queries. I don't like Squirrel, but here are a few things squirrel does that are nice that I wish this did: 1. Auto limit 2. Syntax highlighting 3. Multiple queries can be written in the editor; spaces separate them. This seems to run the first query in the editor afaict. 4. Key bindings (I discovered that cmd-enter appears to run the query, but I didn't see these documented anywhere nor are the configurable.) Also, stylistically it's a little spare. Alternating textures per row might be nice. I do like the live table editing and the quick auto-querying of tables (though, there are cases where I might not like that.) Another thing I like is the query history -- one thing that would be nice would be to highlight those queries that failed due to syntax errors in red or something, to help you read the list, but even more importantly, a search feature (like Sublime's cmd-P).

jakobegger 12y ago
1. I don't really want to modify the SQL the user types in the query 2. Syntax highlighting is hard to get right, but I'll add it eventually. 3. Postico by default runs all the queries, you can use the popup menu at the bottom to toggle between results. Select some text (even discontinuous selection using ⌘) and only the selected part is executed. 4. Key bindings are shown as tooltips (hover over buttons for a few seconds), and you can find more keybindings by looking throught the menus. 5. The history search totally makes sense and I just haven't gotten around to implement it yet.
- uxp 12y ago
  An alternative to syntax highlighting might be query structuring/beautifying (on command, not by default). And +1 from me for search history. Thanks for building these apps. Sequel Pro nails it for MySQL, but up until lately there seemed to be a void on the PG side. I've been using PG Commander for about 5 months and am excited I can use my license on Postico. So far the app works as I expect it to, and looks fantastic.
  - christianpbrink 12y ago
    Can you say more about using your PG Commander license? I have one too but don't understand the connection with Postico. edit: I figured it out. Sorry for the noise.
- jdhendrickson 12y ago
  Casting another vote for 2 and 5. Thanks for all your hard work!

jakobegger 12y ago

1. I don't really want to modify the SQL the user types in the query 2. Syntax highlighting is hard to get right, but I'll add it eventually. 3. Postico by default runs all the queries, you can use the popup menu at the bottom to toggle between results. Select some text (even discontinuous selection using ⌘) and only the selected part is executed. 4. Key bindings are shown as tooltips (hover over buttons for a few seconds), and you can find more keybindings by looking throught the menus. 5. The history search totally makes sense and I just haven't gotten around to implement it yet.

uxp 12y ago
An alternative to syntax highlighting might be query structuring/beautifying (on command, not by default). And +1 from me for search history. Thanks for building these apps. Sequel Pro nails it for MySQL, but up until lately there seemed to be a void on the PG side. I've been using PG Commander for about 5 months and am excited I can use my license on Postico. So far the app works as I expect it to, and looks fantastic.
- christianpbrink 12y ago
  Can you say more about using your PG Commander license? I have one too but don't understand the connection with Postico. edit: I figured it out. Sorry for the noise.
jdhendrickson 12y ago
Casting another vote for 2 and 5. Thanks for all your hard work!