Awk equivalents to SQL query data manipulation
subhadip.ca
subhadip.ca
https://www.gnu.org/software/coreutils/manual/html_node/join...
And to improve the ergonomics, the vnlog wrappers are available to operate on field names, while retaining the internals of the core tools:
guess need to set up a git repository containing the same system written with a)shell/unix tools b) awk/gawk for a separate hn comparison discussion.
Instead of using awk/gawk straight up/out of the box, can code/program awk/gawk or use non-awk/gawk stuff to convert to different format to work around issue.
[edit this when have simple working example:
edit1: one non-awk/gawk way to avoid the cvs comma issue would be to use jq to convert column data to different format.
]
The friction was just so bad that made me hate my job.
https://duckdb.org/docs/data/csv.html
Beyond that I too tend to write something in Node/Python where I can use an IDE etc. Scratch scripts in IDEA's IDEs are great for this.
'console' implies all errors independent of who error message is for (OS, developer, administrator, end user of app/product).
End user messages typically set up within awk language program(s) by developer.
[1] pg. 239 https://progforperf.github.io/Expert_C_Programming.pdf
SQL and Awk are both languages which will have to provide syntax errors if the user behind the terminal—mysql console and awk are both ultimately used through the terminal—gives some ill-formed input.
Awk script stored in file.
In awk file, awk script makes use of mysql interface to generate information to use in awk script to process & return to mysql.
Awk file redirects error messages generated by the awk script to an error log file.
In mysql, aforementioned awk script is called in a different terminal than mysql from within mysql via system().
When/how does the message in the error log file get displayed to the mysql console?
Where does the error(s) generated by the mysql stuff used in the awk script get displayed? Note: example does not state what's done with error message generated by mysql called within the awk script.
Hint: Not to the invoking mysql console screen & maybe also not to the error log file.
edit: The assumption is that awk successfully runs the awk file & within the awk file the mysql api call runs successfully.
Is the mysql api call(s) always worked a good/valid assumption to make without knowing what the 'awk file' handles/does with the mysql api error(s)?
Is mysql & awk script being run on the same system?
Is system set up to log errors to the root console or is that disabled?
Did the printer on the serial console that is suppose to print out/log hard copy of the root console error messages run out of paper at the wrong time?
Great until things tank before getting a return.