Postgres CLI with autocompletion and syntax highlighting (github.com)

I'm the author.

I'm hoping to go public with the MySQL version before the end of this month. So a week or so. :)

Can you tell me which version of pgcli you're running? Can you try upgrading?

\x is implemented and available in the latest version. The ';' enter bug is also fixed in the latest version.

We're still slowly adding more of the back-slash commands supported by psql.

    SELECT * FROM "access" a WHERE a.

wow \x is great, I never knew about that.

I was following the design philosophy of fish shell http://fishshell.com/docs/current/design.html#design-overvie...

Especially these two:

* Configurability is the root of all evil

* The law of discoverability

Yes. You can toggle the multi-line mode by pressing F3. You can also make that permanent by editing the config file in ~/.myclirc

In the multi-line mode a semi-colon signifies the end of a query.

Done! :)

That's the keybindings to use. For example when emacs mode is selected, you can use C-a to jump to home or C-e to jump to the end of the line.

If it is changed to Vi mode then you can hit escape to go to normal mode and then use '0' to jump home or '$' to jump to the end etc.

Have you tried pgadmin, it even has a 'visual' query builder.

There is no native support for ssh port forwarding. But I do support connecting via a socket.

I used licecap (http://www.cockos.com/licecap/) to create that gif.

Redshift is not officially supported since I'm targeting Postgres 9.x.

But there is some work underway to add support for Redshift.

https://github.com/dbcli/pgcli/issues/18

http://www.catb.org/jargon/html/D/DWIM.html

    DWIM: /dwim/

    [acronym, ‘Do What I Mean’]

<snip>

    Warren Teitelman originally wrote DWIM to fix his typos and spelling errors, so it
    was somewhat idiosyncratic to his style, and would often make hash of anyone
    else's typos if they were stylistically different. Some victims of DWIM thus
    claimed that the acronym stood for ‘Damn Warren’s Infernal Machine!'.

    In one notorious incident, Warren added a DWIM feature to the command interpreter
    used at Xerox PARC. One day another hacker there typed delete *$ to free up some
    disk space. (The editor there named backup files by appending $ to the original
    file name, so he was trying to delete any backup files left over from old editing
    sessions.) It happened that there weren't any editor backup files, so DWIM
    helpfully reported `*$ not found, assuming you meant 'delete *'`. It then
    started to delete all the files on the disk! The hacker managed to stop it
    with a Vulcan nerve pinch after only a half dozen or so files were lost.

    The disgruntled victim later said he had been sorely tempted to go to Warren's
    office, tie Warren down in his chair in front of his workstation, and then type
    delete *$ twice.

I'm planning to add confirmation for those commands to make sure people don't accidentally drop something they don't intend to.

I don't think Vim's autocompletion can suggest table names and column names from the current database. I think the advantage of this tool is in using the metadata from the database to suggest relevant completions instead of mere keyword completions.