The specific SQL code "insert ... from select.." implies that the data does not "transit" through the ETL: this is really different from the other SQL codes (i.e. other than some simple "select" or other than some simple "insert, update, delete": These are already handled ok now) and must have a specific code to handle this situation.
Hopefully, there are already many open source libraries (e.g. sqlglot) that handles this "insert ... from select.." situation that is not very complex.
Need to check if we'll use sqlglot library or a brand new original code.
The specific SQL code "insert ... from select.." implies that the data does not "transit" through the ETL: this is really different from the other SQL codes (i.e. other than some simple "select" or other than some simple "insert, update, delete": These are already handled ok now) and must have a specific code to handle this situation.
Hopefully, there are already many open source libraries (e.g. sqlglot) that handles this "insert ... from select.." situation that is not very complex.
Need to check if we'll use sqlglot library or a brand new original code.