Parenthesis highlighting & debug messages
- Dominant language
- Python
- Stars
- 486
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
These may exist already, but I couldn't find where this setting would be enabled in the app.
The best part of postico is that it rarely crashes and it's very lightweight. I migrated from heavy pgadmin iii use because this provides a really slick interface and I can finally escape the pgadmin headaches and tableflipping with it's unstable query editor and frequent crashes.
However, what I think postico really needs is 1. parenthetical highlighting and 2. clearer debug messages. pgadmin iii has both of these and when working on debugging a complex SELECT query in the editor I find myself copying and pasting into pgadmin query editor to figure out if I have unbalanced parentheses and what position of the query is really causing issues (and why).
In short, parenthetical highlighting in the editor would go a long way in beefing up this app. I love doing scratch work and experimenting and exploring in postico, but this missing feature sucks. when the queries become sufficiently complex, it's good to be able to click the cursor at a certain parenthesis and have a visually indication in the query window which other parenthesis it is paired with it. Pgadmin does a great job with this and it's a feature that is oft taken for granted, but once it's gone you really wish you had it.
On a more minor note, the debug messages leave more to be desired. But this would be less of an issue with good query editor syntactic highlights for parenthetical imbalances.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the query editor and reproduce the report using a complex SELECT with unbalanced parentheses. Compare the requested cursor-pair highlighting and clearer debug messages against the current behavior; done means both requests have defined, testable behavior in the editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- desktop, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100