Tcl8.6/Tk8.6 Documentation > tdbc::sqlite3 Package Commands, version 1.0.6 > tdbc_sqlite3
Tcl/Tk Applications | Tcl Commands | Tk Commands | [incr Tcl] Package Commands | SQLite3 Package Commands | TDBC Package Commands | tdbc::mysql Package Commands | tdbc::odbc Package Commands | tdbc::postgres Package Commands | tdbc::sqlite3 Package Commands | Thread Package Commands | Tcl C API | Tk C API | [incr Tcl] Package C API | TDBC Package C API
tdbc::sqlite3::connection create db fileName ?-option value...?
Connection to a SQLite3 database is established by invoking tdbc::sqlite3::connection create, passing it a string to be used as the connection handle followed by the file name of the database. The side effect of tdbc::sqlite3::connection create is to create a new database connection.. As an alternative, tdbc::sqlite::connection new may be used to create a database connection with an automatically assigned name. The return value from tdbc::sqlite::connection new is the name that was chosen for the connection handle. See tdbc::connection(n) for the details of how to use the connection to manipulate a database.
Since the encoding of a SQLite3 database is always well known, the -encoding option accepts only utf-8 as an encoding and always returns utf-8 for an encoding. The actual encoding may be set using a SQLite3 PRAGMA statement when creating a new database.
Only the isolation levels readuncommitted and serializable are implemented. Other isolation levels are promoted to serializable.
The -readonly flag is not implemented. -readonly 0 is accepted silently, while -readonly 1 reports an error.tdbc, tdbc::connection, tdbc::resultset, tdbc::statement TDBC, SQL, SQLite3, database, connectivity, connection