This would be a good chance to outline and fix some of the worst design decisions of the various sqlite hacks and security issues. No stack, so no proper subfu

This would be a good chance to outline and fix some of the worst design decisions of the various sqlite hacks and security issues. No stack, so no proper subfunction model, such as triggers or functions calling other functions. Simple remote queries can be made destructive, due to the extremely hackish design. The horrible, insecure by default text search engine. Unfortunately this guy treats sqlite as a role model of a good design. Maybe he will find out when it's too late. https://github.com/rurban/hardsqlite https://github.com/rurban/hardsqlite