I was trying to use .expert earlier when I found out that if you have a function from an extension in any table's schema, it just does not work. Typing .expert would just immediately result in "sqlite3_expert_new: no such function: {function name}" even when the extension the function comes from is loaded.

Maybe that error is necessary when the function would be called during the query, but in my case I have generated columns on tables which are stored. It shouldn't matter if my SELECT query references one of those columns since it already has the value. It especially shouldn't matter if I'm not even referencing one of those tables, but the .expert call doesn't even get to that point before failing.

Example:

SQLite version 3.37.0 2021-07-31 20:30:41
Enter ".help" for usage hints.
sqlite> .load ./Extensions/sql_functions
sqlite> .expert
sqlite3_expert_new: no such function: IP_TO_INT
sqlite> SELECT IP_TO_INT('127.0.0.1');
2130706433

As a workaround I was able to just create an in-memory version of the database with the generated columns replaced by regular columns, but I figured I should mention it here.

Because the .expert facility creates new database connections to achieve some of its functionality, those extension functions need to be available for those connections too, along with the one you explicitly create.

The extension load/usage options described in Automatically Load Statically Linked Extensions and Persistent Loadable Extensions can be used to arrange that availability and cure the problem you see without having to modify your schema.

I agree that such improvements are due. I'll see to them soon.