The key reason for storing procs in the database is that you execute the SP code in the same process as the SQL engine. This makes sense for database engines designed to act as a network-connected service, but the imperative of SQLite is much less. Given that it works as a DLL in your current process, it makes sense to implement SP in the client language.
However, you can extend SQLite with your own custom host language functions (PHP, Python, Perl, C #, Javascript , Ruby , etc.). I did this in C # using DevArt SQLite to implement password hashing.
Tony o'hagan
source share