As a terminal user, nearly all the time, I'm mostly inside the terminal so they don't make as much sense to me.
However I'm not _always_ a terminal user. Sometimes I'm a browser user and sometimes I have to use spreadsheets too.
In these contexts I use other programs which have GUI's, sometimes quite minimal, like a screenshot app for example.
I can certainly imagine getting a spreadsheet into a defined set of columns and then executing another app which asks a set of questions and then does something with that data, maybe even only draws a graph (as I despize drawing graphs in spreadsheets).
In this context, I feel that I may well write BASH, but opening a terminal would be as jarring as leaving it under normal circumstances...
So I feel these kind of tools are useful.
Shameless plug: Funnily I'm working on the opposite. Integrating STDIN/STDOUT into the GUI via a WebView, because I want that command line control but I there are occasions where there are benefits in using a GUI (graphs etc) - https://github.com/forbesmyester/wv-linewise
He veered off into that Salisbury thing and I agree with him about the quality and some of the stretches made in the BBC output but not his conclusions. Other things are too off piste for me too...
However that does not mean to say his observations are void. I believe he is writing the facts as he sees them (and not fiction), of course there is opinion mixed in...
Naff tables (along with poor graphs) was one of my key motivations to create WV Linweise, which spawns a tiny web renderer to make displays nicer... Love the terminal, but some things it is just not great at...
Authentication is not handled at all. Given it is a project with a front and back end (using a REST interface between) I think the correct approach is to do authentication on a load balancer. The approach is fully documented here: https://github.com/forbesmyester/esqlate/issues/5
That is true, and I considered this approach. But DB procedures cannot link to each other and the target users are different - giving some people a DB procedure is much harder than giving them a web interface.
It might be the instructions for install a bit off but I've tested on MacOS and Ubuntu (both BASH)... Which method is your install? If it's Docker Compose ( https://github.com/forbesmyester/esqlate#docker-compose-meth... ) it has a BASH line there in the README that does the checkout for you.
Yeh sounds like you had a similar revelation to me :-) This can also do the linking between "reports" or "forms". Happy you built one, makes me think this has at least some chance of success.
You write the SQL into a JSON file. Users then can then execute that SQL with their own parameters. So the many-to-many is in your capability... A key reason for this is that it itself should not be clever.
Yeh. It send through the key/values in HTTP POST and then you have the SQL and K/C's on the server, the SQL itself is not sent. Server passes them through as parameters to the Node.JS `pg` module so that takes care of defeating SQL injection.
It lets you follow a semantic API path through multiple API calls.
https://github.com/stepci/stepci/blob/main/examples/captures...