Some issues during first time testing vdsql about visidata HOT 5 OPEN

Just gave the (stable?) version 0.2 of vdsql a spin, with even less success:

❯ vdsql mysql://root:@localhost/mysql
Traceback (most recent call last):
  File "/root/.venv/visidata/bin/vdsql", line 5, in <module>
    from vdsql.__main__ import main
  File "/root/.venv/visidata/lib/python3.9/site-packages/vdsql/__init__.py", line 2, in <module>
    from ._ibis import *
  File "/root/.venv/visidata/lib/python3.9/site-packages/vdsql/_ibis.py", line 8, in <module>
    from visidata.pyobj import ExpandedColumn
ImportError: cannot import name 'ExpandedColumn' from 'visidata.pyobj' (/root/.venv/visidata/lib/python3.9/site-packages/visidata/pyobj.py)

from visidata.

Thanks for the report, @p3k. Ibis development happens at a very fast pace (there have been 6 major releases in the <2 years since vdsql was first implemented), and so things change faster than we can adapt to them. For example, sqlalchemy is no longer required by ibis, and we've removed the dependency from vdsql, we just haven't released a new version yet.

Note: I can see the stacktrace but I do not know how to copy it without the surrounding TUI getting in the way 🤷 (How can I hide the status box‽)

You can see the stacktrace with Ctrl+E, and either save it from there with Ctrl+S, or copy it to your system clipboard with gsgzY if you have that set up. We're aware of the status box being in the way; b should toggle it on/off, but it's often more frustrating than that. It's top of my list for a 3.1 release.

The other issues you mentioned could use a little attention too. Thanks again and sorry for the frustration.

from visidata.

Hi @saulpw – thanks for your swift reply!

I hope I did/do not sound too frustrated, that was not my intention. I am always delighted when I invoke vd, how well it works and how easy I can work even with huge data. It is a great piece of software! 🤩

Sorry to hear the Ibis integration is so stressful – I do not wish to add to the pressure. Just was curious to try out vdsql (and version 3 of visidata)…

True, the status box can be a bit irritating – although I generally like its idea, and the quirky quotes (I feel quirky sometimes).

Maybe immediately advertise the ctrl+b key binding as toggle for the box on first display? Also, I was looking for something with “status” in the view menu – would not have thought of “sidebar”!

Thanks for the help to save the stack trace – I updated the issue description with the complete output. (Unfortunately, I cannot use a clipboard tool because visidata and the database are running on a remote machine… oh, and what is gsgzY? A search for it did not yield any meaningful results 🤷 )

from visidata.

Thanks, @p3k, I appreciate the kind words!

Maybe immediately advertise the ctrl+b key binding as toggle for the box on first display?

There is a note at the bottom of the sidebar saying exactly that. It's not there for the status messages because those can't be disabled--but if you invoke any command, even just a move/click, it will dismiss the status sidebar and bring up the sheet-specific sidebar.

oh, and what is gsgzY?

• gs to select all rows
• gzY to copy values in the current column for selected rows into the system clipboard

from visidata.

Ah, gsgzy is a keyboard combo! 💡 My mind went into a very different direction 😅

Re the note at the bottom of the status box: I now saw it ☺️

from visidata.