I have too agree with Kees Nuyt here. I am quite comforatble and successful in adding "storage providers" as virtual table implementations for stuff as diverse as Faircom CTree files, a proprietary memory section based data dictionary, elements of a linux queue and whatever else we need here. Currently I am experimenting with a VFS that allows an SQLite database file to reside in a shared memory section. There have been several attempts to save SQLite bytecode in lieu of stored procedures, but I am not aware that any of these have resulted in anything useful. I don't expect them to either, as SQLite bytecode is specifically generated for the current combination of schema and statement and needs to be recompiled as soon as the schema of the affected tables is changed.