sqlite3_overload_function

Declare that a function has been overloaded by a virtual table.

If the function already exists as a regular global function, then this routine is a no-op. If the function does not exist, then create a new one that always throws a run-time error.

When virtual tables intend to provide an overloaded function, they should call this routine to make sure the global function exists. A global function must exist in order for name resolution to work properly.

sqlite3_overload_function()

Declare that a function has been overloaded by a virtual table.

If the function already exists as a regular global function, then this routine is a no-op. If the function does not exist, then create a new one that always throws a run-time error.

When virtual tables intend to provide an overloaded function, they should call this routine to make sure the global function exists. A global function must exist in order for name resolution to work properly.

sqlite3_overload_function()

Declare that a function has been overloaded by a virtual table.

If the function already exists as a regular global function, then this routine is a no-op. If the function does not exist, then create a new one that always throws a run-time error.

When virtual tables intend to provide an overloaded function, they should call this routine to make sure the global function exists. A global function must exist in order for name resolution to work properly.

sqlite3_overload_function()

Declare that a function has been overloaded by a virtual table.

If the function already exists as a regular global function, then this routine is a no-op. If the function does not exist, then create a new one that always throws a run-time error.

When virtual tables intend to provide an overloaded function, they should call this routine to make sure the global function exists. A global function must exist in order for name resolution to work properly.

sqlite3_overload_function()

Declare that a function has been overloaded by a virtual table.

If the function already exists as a regular global function, then this routine is a no-op. If the function does not exist, then create a new one that always throws a run-time error.

When virtual tables intend to provide an overloaded function, they should call this routine to make sure the global function exists. A global function must exist in order for name resolution to work properly.

sqlite3_overload_function()