SQLITE_CREATE_INDEX(3) | Library Functions Manual | SQLITE_CREATE_INDEX(3)

# NAME

`SQLITE_CREATE_INDEX`, `SQLITE_CREATE_TABLE`, `SQLITE_CREATE_TEMP_INDEX`, `SQLITE_CREATE_TEMP_TABLE`, `SQLITE_CREATE_TEMP_TRIGGER`, `SQLITE_CREATE_TEMP_VIEW`, `SQLITE_CREATE_TRIGGER`, `SQLITE_CREATE_VIEW`, `SQLITE_DELETE`, `SQLITE_DROP_INDEX`, `SQLITE_DROP_TABLE`, `SQLITE_DROP_TEMP_INDEX`, `SQLITE_DROP_TEMP_TABLE`, `SQLITE_DROP_TEMP_TRIGGER`, `SQLITE_DROP_TEMP_VIEW`, `SQLITE_DROP_TRIGGER`, `SQLITE_DROP_VIEW`, `SQLITE_INSERT`, `SQLITE_PRAGMA`, `SQLITE_READ`, `SQLITE_SELECT`, `SQLITE_TRANSACTION`, `SQLITE_UPDATE`, `SQLITE_ATTACH`, `SQLITE_DETACH`, `SQLITE_ALTER_TABLE`, `SQLITE_REINDEX`, `SQLITE_ANALYZE`, `SQLITE_CREATE_VTABLE`, `SQLITE_DROP_VTABLE`, `SQLITE_FUNCTION`, `SQLITE_SAVEPOINT`, `SQLITE_COPY`, `SQLITE_RECURSIVE` —
Authorizer Action Codes

# SYNOPSIS

`#define SQLITE_CREATE_INDEX`
`#define SQLITE_CREATE_TABLE`
`#define SQLITE_CREATE_TEMP_INDEX`
`#define SQLITE_CREATE_TEMP_TABLE`
`#define SQLITE_CREATE_TEMP_TRIGGER`
`#define SQLITE_CREATE_TEMP_VIEW`
`#define SQLITE_CREATE_TRIGGER`
`#define SQLITE_CREATE_VIEW`
`#define SQLITE_DELETE`
`#define SQLITE_DROP_INDEX`
`#define SQLITE_DROP_TABLE`
`#define SQLITE_DROP_TEMP_INDEX`
`#define SQLITE_DROP_TEMP_TABLE`
`#define SQLITE_DROP_TEMP_TRIGGER`
`#define SQLITE_DROP_TEMP_VIEW`
`#define SQLITE_DROP_TRIGGER`
`#define SQLITE_DROP_VIEW`
`#define SQLITE_INSERT`
`#define SQLITE_PRAGMA`
`#define SQLITE_READ`
`#define SQLITE_SELECT`
`#define SQLITE_TRANSACTION`
`#define SQLITE_UPDATE`
`#define SQLITE_ATTACH`
`#define SQLITE_DETACH`
`#define SQLITE_ALTER_TABLE`
`#define SQLITE_REINDEX`
`#define SQLITE_ANALYZE`
`#define SQLITE_CREATE_VTABLE`
`#define SQLITE_DROP_VTABLE`
`#define SQLITE_FUNCTION`
`#define SQLITE_SAVEPOINT`
`#define SQLITE_COPY`
`#define SQLITE_RECURSIVE`

# DESCRIPTION

The sqlite3_set_authorizer() interface registers a callback function that is invoked to authorize certain SQL statement actions. The second parameter to the callback is an integer code that specifies what action is being authorized. These are the integer action codes that the authorizer callback may be passed.

These action code values signify what kind of operation is to be authorized. The 3rd and 4th parameters to the authorization callback function will be parameters or NULL depending on which of these codes is used as the second parameter. The 5th parameter to the authorizer callback is the name of the database ("main", "temp", etc.) if applicable. The 6th parameter to the authorizer callback is the name of the inner-most trigger or view that is responsible for the access attempt or NULL if this access attempt is directly from top-level SQL code.

# SEE ALSO

sqlite3_set_authorizer(3)

December 19, 2018 | NetBSD 9.0