You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Developers are advised to avoid using the SQLITE_INNOCUOUS flag for application-defined functions unless the function has been carefully audited and found to be free of potentially security-adverse side-effects and information-leaks.
SQLITE_DIRECTONLY is now available in better-sqlite3version 7.3.0 via the directOnly: true option. I'm hesitant on adding SQLITE_INNOCUOUS until I understand a good use-case.
I'd like to be able to define custom functions or aggregates and mark them as SQLITE_DIRECTONLY or SQLITE_INNOCUOUS.
The text was updated successfully, but these errors were encountered: