neilotoole

5 ms·

1.
by neilotoole 2y ago
That's an unfortunate naming clash. This "sq" (sq.io) predates the sequoia "sq" by several years I believe.
2.
by neilotoole 2y ago
Developer here. Thanks for the kind words. Substring matching is on my short list (also totally open to a PR!).
3.
by neilotoole 2y ago
You can already install sq using several of the common package managers, or build from (Go) source if you prefer. https://sq.io/docs/install
4.
by neilotoole 2y ago
> I'm not really seeing anything I can't do with standard SQL and CLI tools like psql. Developer here. There's a few features other than the query stuff that I still think are pretty handy. The "sq inspect" stuff
5.
by neilotoole 2y ago
The theory at the time was that if "SQL" is pronounced like "sequel", and "sq" is just dropping the "L" from "SQL", then "sq" must be... I suspect the uptake on the "seek&quot
6.
by neilotoole 2y ago
Developer here. That was exactly the target audience. Note that sq doesn't just handle relational DBs, it also has (varying quality) support for CSV, JSON, Excel, and so on. At the time (2013) I wasn't aware of a convenient one-li
7.
by neilotoole 2y ago
> How would I know its outputting the correct SQL? If you mess up joins you end up with bad output. The generated SQL is output in sq's logs, when logging is enabled. https://sq.io/docs/config#logging
8.
by neilotoole 2y ago
I'm not GP, but I am the sq developer. > the person just thought “this would be cool to have” and implemented it. Correct. This is true of much OSS, or at least I've always suspected so.
9.
by neilotoole 2y ago
> It's a weird trend that seems almost entirely motivated by people wanting open source projects in their resume Developer here. I can't speak to what you see as the weird trend, but I can speak about sq's history: - I cre