martingms / vipsql Goto Github PK

Is there a way to :set nowrap on the output from the select statements?

Hello! Is there a way to send the password though the buffer when prompted?

I normally open vipsql over an .sql file I already have, then work on it, save, and so on.

In the past days I've lost a bunch of queries I was writing on the [Scratch] file because I was dumb and closed it without realizing it wasn't a file I had.

I don't know how to solve this, maybe save [Scratch] sessions on /tmp/ somehow?

I'm using Gentoo Linux. I have some bluehost webspace that has a postgresql database.

I know everything is configured properly on the bluehost database side because this command works and drops me into the postgresql terminal:

voyager:el@~ $ psql --host=10.20.30.40 -U my_username -d machines_testing -p 5432
psql (9.5.3, server 8.4.20)
Type "help" for help.
machines_testing=> select 'foo';
 ?column?
----------
 foo
(1 row)

However when I use the same command for vipsql, the plugin doesn't create a channel.

vipsql --host=10.20.30.40 -U my_username -d machines_testing -p 5432

I try to send a command and I get an error:

Error detected while processing function <SNR>3_Send:
line   11:
Attempted send on a closed channel

I know that things are okay on the vipsql side because it connects correctly to the local postgresql database with this command:

vipsql -Upostgres -d postgres

I can send sql commands and run them as expected.

It appears that vipsql is interpreting the bash parameters passed in and interpreting some of them as new files to open. I've tried putting things in quotes and using all the variations to communicate to vipsql the config options, and all are met with some kind of error.

Is there a streamlined way for me to specify host, port, username, database and password? passing it via bash params seems to be problematic. Maybe there's a silly workaround with escapes and quotes?

Something like a ================================== (or perhaps something better).

DROP TABLE
CREATE TABLE
INSERT 0 1
 id |         created_at         |                                             data                                             
----+----------------------------+----------------------------------------------------------------------------------------------
  1 | 2017-09-28 21:36:29.828107 | {"ok": {"pli": true}, "amt": 12, "cred": "xyz", "debs": ["pli"], "txns": [], "asset": "BRL"}
(1 row)

==================================
ERROR:  relation "users" already exists
DROP TABLE
CREATE TABLE
INSERT 0 1
 id |         created_at         |                                             data                                             
----+----------------------------+----------------------------------------------------------------------------------------------
  1 | 2017-09-28 21:36:40.489839 | {"ok": {"pli": true}, "amt": 12, "cred": "xyz", "debs": ["pli"], "txns": [], "asset": "BRL"}
(1 row)

Sometimes is difficult to read the results buffer when a lot of errors and "CREATE STUFF" statements are being logged.

It would be great to have neovim support.

I don't know exactly what are the conditions for this to happen, but I was working with the two buffers, vertically separated, one containing my SQL statements and the other the default __vipsql__ output buffer. I then opened a new one with more SQL statements, again in a vertical split, and issued a vipsql command from it. The output of the command was appended to my previous buffer with my own SQL commands (which happened to be linked to a file on disk).

I don't understand the vim internals, so forgive me.

Anyway, just a minor bug. vipsql is an amazing plugin, it has changed my life.

Thanks for writing this excellent plugin.
The only issue I can see is that queries appear one after the other, but are not visible. Would it be possible to modify the code so that the window scrolls down so that the new query result is at the top?

This is amazing! Thanks so much for writing this!

I was just in Olso recently for the NDC conference.
Too bad I didn't get a chance to meet you.
Keep up the great work!