I like the idea. It lacks some important functionality e.g. \x does not work. This is a feature I use regularly in the psql command line tool.
Also, I'm not sure if it's a bug, but with Smart Completion set to off, it still auto completes as you are typing. This can get annoying after a while. Lastly, if you type ';' followed by enter, the program crashes.
For the record, the standard psql already supports auto-completion, albeit with much less pretty interface (a common readline-style horizontal candidate listing). Syntax highlighting seems great, though.
Informmix isql tool used to have a form mode, where one could:
* select table or form from a list, hit enter
* then a form with all fields would show up
* one could populate some fields with query condition, e.g. name = 'xyz'
* then hit enter and tool would run a query
* then one could navigate prev/next through the results.
I was not fond of this, but some folks in the office still swear by this and ask if they can have a tool like that for postgres. I sent them to psql, but just typing SQL gives them heartburn.
I must admit some of them were quite faster with isql than with psql. This tool helps a bit, but still hoping for the form mode.
My support folks have only terminal access. Sure, they could tunnel pgadmin in (via SSH) if they knew how and even what they are doing. As such they are stuck with command line only.
I've been using this for a while and it's great. The author is also excellent at running open source projects. Great mentality. I thought this was posted to HN a while ago but I could be mistaken. Definitely worth the re-post if it was.
I have been using this in production for a few weeks now and I quite like it. A real improvement over most of the CLI interfaces I have even with my expanded and frankly bloated .psqlrc.
This is great! I'm thrilled to finally see something like this.
I have a question, mostly about MySQL version of it: have you made some effort to natively support SSH port-forwarding/tsocks with this client? Because my experience is that it really works bad with the default client. But, TBH, I don't even know how much it depends on the client/server-side.
Realy nice, thanks! What would be the added value of this compared to using vim handling autocompletion and syntax highlighting for editing queries and tmux for the output?
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.
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 used that system, Interlisp, the Warren Teitelman version of LISP, on SRI's DECsystem 2060. I had a similar experience. I typed "EDIT" when in the wrong mode, and got "=EXIT" from DWIM. Interlisp terminated without saving.
It really was keyed to Warren's errors. It would try to correct "9" and "0" into "(" and ")", a mistake he apparently made frequently but I never did.
I also used InterLisp. I had a Xerox 1108. The first 5 minutes I used my 1108 my mind was blown when it corrected a typo in a short program I entered and ran.
It's been in private beta for backers for a while. I forget when it's going public, but I don't think it's far away...