With sqlite3_expanded_sql() you can retrieve the expanded version of the sql statement with the bindings. This is useful mostly for debugging purposes but could be useful if one has a disaster recovery process utilizing the prepared sql statements. Since sqlite3 has provided this as part of the api it may be nice to utilize here instead of creating an alternative process for creating that expanded sql.
Proposed implementation
Wondering if maybe Statement could have a expandedSql() method that could be used for this - always just pulls the sql:
Summary
With sqlite3_expanded_sql() you can retrieve the expanded version of the sql statement with the bindings. This is useful mostly for debugging purposes but could be useful if one has a disaster recovery process utilizing the prepared sql statements. Since sqlite3 has provided this as part of the api it may be nice to utilize here instead of creating an alternative process for creating that expanded sql.
Proposed implementation
Wondering if maybe Statement could have a expandedSql() method that could be used for this - always just pulls the sql:
Also could see this being in the trace as well.
Here is my quick use of the api performs the same result on a prepared statement: