amjith

Love the site design. Excited to try it out.

This is fantastic. I'm a huge fan of No Such Thing as a Fish podcast.

Are you part of club fish? I bet the folks in the discord channel would love this.

I'm working on a mountain biking app to compare trails that I've ridden.

https://trailcompare.com/

Imports data from strava and lets me search and compare multiple rides.

The trail name detection only works in SantaCruz (CA) area.

Can you elaborate what this means?

Typesense was relatively strict with matches compared to other engines.

Perhaps an example to clarify the statement?

I've been loving mycli for the last 4 years or so.

So rewarding to hear this. Cheers!

The latest version of pgcli is pypi was released on Dec 11 2020. There are only a few changes unreleased in the master branch.

https://github.com/dbcli/pgcli/blob/master/changelog.rst

What feature are you waiting for? I can talk to the project lead to see if we can push out a new release if needed.

They are both supported in mycli and pgcli clients.

How is the search implemented?

Does anyone know if haiku can run Python 3? I know that haiku comes with Python but thedefault version is 2.7.

Thank you for the kind words. It's always nice to hear from happy customers .

Thank you, Simon. That means a lot coming from the author of datasette. I love your work.

Damn it! :)

We don't support all of the special commands but we do support a small subset of them. We support .mode .schema, .table and a few others.

Haha. No.

We have a large set of tests, but the coverage is no where close to the level that SQLite has.

DBCLI (https://www.dbcli.com/) is an open source org that made pgcli, mycli, mssql-cli etc.

LiteCLI is part of that org. So you can think of it as a clone of mycli that happens to work with SQLite.

The code base is largely similar between mycli and litecli. The changes are to support the SQLite backend and to support the dot commands (like .tables, .mode etc).

So the feature set should be same.

The DBCLI tools are not created by a single individual (anymore). We have a team of core devs and the lead maintainer for pgcli, mycli and litecli are all different people.

I have a few recommendations for you.

We use `less -XRF` by default. You can change this to whatever you want via the config file `~/.config/litecli/config`. Just uncomment the line that says `# pager = "less -SXRF".

Adding the `-S` to the list of options will make it much better. It will not wrap long lines but instead it will enable horizontal scrolling (using arrow keys). Check for pager section on this page for some details: https://litecli.com/output/

The other option is to set the `auto_vertical_output = True` in the config file.

This option will cause results to be displayed vertically if they are too wide for the current window.

I'm a core dev in the project. Happy to answer questions.

Code: https://github.com/dbcli/litecli

It is based on the pgcli/mycli tools for Postgres and MySQL. It is the newest addition to the https://www.dbcli.com suite of tools.

https://github.com/dbcli/mssql-cli

I'm the creator of dbcli. I can give you my perspective.

usql is a great tool if you're familiar with Postgres' psql client and wish you could use it for other databases like MySQL, Cassandra etc.

dbcli tools are designed to preserve the usage semantics of the existing tools but improve on them by providing auto-completion. For instance you can use `\d` in pgcli and `SHOW TABLES` in mycli. This was a conscious decision to make pgcli and mycli drop in replacements for of MySQL and psql. I was also working under the assumption that people rarely use multiple databases, you're either a postgres shop or a MySQL shop. If you have a mix of both, there is a good chance that not a single person is interacting with both of them on a daily basis. You have different teams using different databases. But my reasoning there could be flawed.

There is nothing stopping someone from adding an adapter to the usql tool to make it behave like MySQL (because they like the mysql client better) based on a command line argument, for instance.

You've created something useful and it will save a lot of programmers a ton of time.

I didn't find your writing insufferable. I've written tongue in cheek (or over the top) posts about my projects in the past. If they can't see the humor and the usefulness of the project, their loss.

Thank you for creating Glom and thank you for posting it on HN. Count me in as one of your users.

Thanks for the plug. I'm the author of the failover piece. Happy to answer questions.

I did a similar library for Python (~3yrs ago).

blog: http://blog.amjith.com/fuzzyfinder-in-10-lines-of-python

library: https://github.com/amjith/fuzzyfinder

I haven't done any benchmarking to check the performance. Feedback welcome.

it's significantly easier to work with

Can you please elaborate?

One of the core devs have expressed interest in creating an sqlite version. But work hasn't started. If you would like to chip in we would be happy to support you in every which way.

Indeed. Prompt-toolkit was instrumental in the design of all these tools. :)

Thank you!

Fish shell's design doc [0] was a huge inspiration in the design of pgcli [1] and mycli [2].

Thank you for leading the charge on modern command line design.

[0] https://fishshell.com/docs/current/design.html

[1] https://www.pgcli.com

[2] https://www.mycli.net

He was the president of Django Software Foundation while running the startup.

So naturally he was a big proponent of Django and his stack was written completely in Django.

The reason being the format change will be jarring to someone who is not used to seeing the expanded mode.

But you bring up a good point. I'm not mired by maintaining legacy, so I could take this as an opportunity to educate users about the \x auto by enabling it as default.

You can change this to an empty space via the config file right now. In ~/.config/pgcli/config look for continuation prompt and set it to empty string.