On 11/15/17, aUser <[email protected]> wrote: > Is it possible (and useful), to generate SQLite bytecode instead of a SQL > statement?
It is neither possible nor useful. The bytecode changes from one release to the next - it is not stable. We treasure this design freedom and will not yield it. In the current bytecode design, if arbitrary bytecode (that is to say, bytecode not generated by SQLite itself) is supplied, then there are many paths that could result in memory corruption, database corruption, assertion faults, segfaults, memory leaks, and other bad things. Adding the extra logic to defend the bytecode against such problems would slow down SQLite for everybody, which we are not willing to do. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
