Up to now, most SQL statements were parsed, then prepared before
execution.
Only individual TSQLRecord content retrieval was using prepared statements.
For the upcoming version 1.12 of the framework, we added an internal SQL
statement cache in the database access.
That is, if a previous SQL statement is run with some parameters, a prepared
version, available in cache, is used, and new parameters are bounded to it
before the execution by SQLite3.
In some cases, it can speed the SQLite3 process a lot.
