SQLITE3_VERSION(3) | Library Functions Manual | SQLITE3_VERSION(3)

# NAME

`sqlite3_version`, `sqlite3_libversion`, `sqlite3_sourceid`, `sqlite3_libversion_number` —
Run-Time Library Version Numbers

# SYNOPSIS

const char sqlite3_version[];

const char *
`sqlite3_libversion`(void);

const char *
`sqlite3_sourceid`(void);

int
`sqlite3_libversion_number`(void);

# DESCRIPTION

These interfaces provide the same information as the SQLITE_VERSION, SQLITE_VERSION_NUMBER, and SQLITE_SOURCE_ID C preprocessor macros but are associated with the library instead of the header file. Cautious programmers might include assert() statements in their application to verify that values returned by these interfaces match the macros in the header, and thus ensure that the application is compiled with matching library and header files.

    assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER ); assert(
    strncmp(sqlite3_sourceid(),SQLITE_SOURCE_ID,80)==0 ); assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0
    );

The sqlite3_version[] string constant contains the text of SQLITE_VERSION macro. The sqlite3_libversion() function returns a pointer to the to the sqlite3_version[] string constant. The sqlite3_libversion() function is provided for use in DLLs since DLL users usually do not have direct access to string constants within the DLL. The sqlite3_libversion_number() function returns an integer equal to SQLITE_VERSION_NUMBER. The sqlite3_sourceid() function returns a pointer to a string constant whose value is the same as the SQLITE_SOURCE_ID C preprocessor macro. Except if SQLite is built using an edited copy of the amalgamation, then the last four characters of the hash might be different from SQLITE_SOURCE_ID.

# SEE ALSO

SQLITE_VERSION(3)

December 19, 2018 | NetBSD 9.1