trdsql VS null

Apparently, there were many who thought the same thing; Tools to execute SQL against CSV were trdsql, q, csvq, TextQL. They were highly functional, hoewver, had many options and no input completion. I found it just a little difficult to use.

Nice! Kinds of reminds me of trdsql

trdsql(https://github.com/noborus/trdsql) is a tool that executes SQL for files such as CSV, but it can also be used by connecting to MySQL. Therefore, SQL such as CREATE TABLE table AS SELECT * FROM csvfile.csv can also be executed.

trdsql can execute SQL against CSV, LTSV, JSON and TBLN, and the database can also use SQLite,PostgreSQL and MySQL.

trdsql can execute SQL against CSV, LTSV, JSON and TBLN, and the database can also use SQLite,PostgreSQL and MySQL.

Check out https://github.com/noborus/trdsql

The trdsql I made is feature-rich and fast (as a similar SQL tool).

Use-case: working on PATCH requests, the body may or may not contain nullable values. I am using guregu/null and I can't use a pointer because if the json contains "null" as a value, the pointer will be set to nil in the struct, instead of a value representing the presence of null. In short I can't differentiate the absence of the field in the request from the presence of the field with a null value.

https://github.com/guregu/null is an awesome package implementing most SQL scanner Interfaces plus JSON

There’s also this: https://github.com/guregu/null

Unfortunately in Go, switching to *bool makes the api a little more awkward to use since users that need to set true or false have to define a local variable then use a pointer to that. Another option would be something like null, but that adds a dependency to your currently-dependency-free project. If anyone has a better solution to this pattern, I'd love to hear it.