Hacker News

Not OP, but I personally put off using a UI for years before finally trying a few and eventually settling on Postico for Mac. I still jump to psql often, but for me it's an accumulation of small quality-of-life improvements:

- results are formatted nicely by default; no more doing a first query, getting too many columns so results wrap unreadably, then changing the columns for a second query, and so on

- manually editing rows is as easy as with a spreadsheet; of course hopefully you don't have to do this often...

- I can change common filters & sorts in the UI with a few clicks instead of having to change SQL; sure, the SQL would only require typing a few characters, but if it's 2 clicks vs. 8 characters, it's still a small win

Downsides are:

- the GUI has an interface for saving queries, but it refuses to let me save them to a subfolder of my project; it wants to save them all in some global location. This doesn't seem good for sharing queries

- if you are doing more complicated sorting or aggregation, it's still easier to just go to psql than to fiddle with the GUI

a big one for me is being able to jump between/search for tables and preview their rows, columns, and indexes quickly; especially when there are many tables/schemas and i don't remember their names

another one is a more comfortable editing experience for queries

Yeah. Reminds me of k9s.

thank you! support for other DBs is planned, starting with mysql and sqlite. no set timeline yet though

Generally if you put a space before your command it'll bypass the history, though depending on your *nix you might need to set `HISTCONTROL=ignoreboth` in your bashrc or similar if it's not already.

Agree that it would be nice to specify credentials a different way - however as a workaround: some bash-based shells support prefixing the command with a space as a way of not saving that command into history.

Ref: https://www.gnu.org/software/bash/manual/html_node/Bash-Vari...

`psql` allows for putting your credentials in a dotfile with a very simple syntax. Should be quick to add support for, and would create a seamless onboarding experience for people who are already using `psql`.

that makes sense, thank you for opening an issue!

I only looked at the linked file, so I'm not going to speak to the rest of the code and don't really have a good grasp of the architecture here.

This seems mostly ok. The only thing that (imo) wouldn't pass code review is that big honking loop at https://github.com/achristmascarl/rainfrog/blob/main/src/app.... That thing needs to be refactored down to be readable, with individual logic chunks being put into their own functions and tidied up a bit.

That's not really Rust-specific, obviously, but all the `match` and `if let` and whatever other Rust stuff looks fine, so it's what I've got.

nope :)

There are a bunch of these, like [1] and [2], probably a lot more.

--

1: https://harlequin.sh/

2: https://www.pgcli.com/

Gobang seems stagnated (no PRs merged since last year), which is a shame.

main reason was that it hadn't been updated in a while. i also wanted the query editor to be more flexible / not limited to just filtering

thank you! and noted :)

What are some of the issues?

it does not unfortunately; open to suggestions about common slash commands ppl would like to see included as shortcuts!

I've been using both.

Charm/bubbletea toolstack, is very much focused on an ELM style architecture, I.e. message passing and deriving UI from state. You can still do immediate type UI if that is what you prefer, but it won't fit with any of the standard components. Bubbletea is a framework more or less, so even if you know Go, it will require you to learn how to build to its strengths.

Ratatui is by default not very opinionated about how to handle state and updates, which requires some development from you, or using a third party library to get an opinionated architecture around it. Ratatui is more of a collection of libraries, out of the box, it expects a certain interface for components, but it is up to you how you want to compose them together. Whether that is immediate-, stateful-, react-, or ELM style. Stateful is the default for all their examples.

Charms way of doing terminal UI is very much based around strings, which can sometimes give issues with spacing, as components can be fiddly to be constrained within a certain space.

Ratatui creates UI on top of a matrix of bytes, which makes it more difficult to do easy things, but allows you to more easily build complex uis.

Generally I prefer Ratatui, as you can really build robust and fast uis on top of it. It does take a bit more work to get started though. I am also biased by Rust tho.

I second this, could some also add C#'s "Spectre.Console" https://github.com/spectreconsole/spectre.console