re: > see information about sql queries from shell command line. aka nosql - oci cli [1]
Note: field orders must be same for remote odbc & local rust data.
remote odbc ordered dumping of 'sql query' in json format to file 1.
local rust ordered dumping of 'sql query' in json format to file 2.
Do a diff between file1 & file2. 'empty result', specified types match.
non-empty result, then may be a more data in one file than other, type mismatches, 'name' mismatches, or something else.
sticking to the 'only use sql' theme:
Instead of file1 and file2, can dump to temporary table1 and temporary table2.
'Flatten' each individual json record before table insertion! (may need to introduce record order number as index.)
json for file1 is in single column, json for file2 is in single column. join on 'string similarities'. -- 'null values' in one field but not in another indicate unmatched pair. -- may be data type or 'value type', requiring additional sql query to get at needed data type mismatch.
Note: field orders must be same for remote odbc & local rust data.
remote odbc ordered dumping of 'sql query' in json format to file 1.
local rust ordered dumping of 'sql query' in json format to file 2.
Do a diff between file1 & file2. 'empty result', specified types match. non-empty result, then may be a more data in one file than other, type mismatches, 'name' mismatches, or something else.
sticking to the 'only use sql' theme:
Instead of file1 and file2, can dump to temporary table1 and temporary table2.
'Flatten' each individual json record before table insertion! (may need to introduce record order number as index.)
json for file1 is in single column, json for file2 is in single column. join on 'string similarities'. -- 'null values' in one field but not in another indicate unmatched pair. -- may be data type or 'value type', requiring additional sql query to get at needed data type mismatch.