Embeddable SQL Database Engine
SQLite is a C library that implements an embeddable SQL database
engine. Programs that link with the SQLite library can have SQL
database access without running a separate RDBMS process.
SQLite is not a client library used to connect to a big database
server. SQLite is a server and the SQLite library reads and writes
directly to and from the database files on disk.
SQLite can be used via the sqlite command line tool or via any
application that supports the Qt database plug-ins.
- Developed at server:database
- Sources inherited from project openSUSE:Factory
-
8
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/sqlite3 && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
baselibs.conf | 0000000105 105 Bytes | |
sqlite-autoconf-3190200.tar.gz | 0002542613 2.42 MB | |
sqlite-doc-3190200.zip | 0005577171 5.32 MB | |
sqlite-fts5-link.patch | 0000000437 437 Bytes | |
sqlite3.changes | 0000109868 107 KB | |
sqlite3.spec | 0000005166 5.04 KB |
Revision 97 (latest revision is 153)
Dominique Leuenberger (dimstar_suse)
accepted
request 498338
from
Ismail Dönmez (namtrac)
(revision 97)
- Update to 3.19.2 * Fix a bug in the LEFT JOIN flattening optimization. Ticket cad1ab4cb7b0fc. * Fix more bugs in the LEFT JOIN flattening optimization. Ticket 7fde638e94287d2c. - Update to 3.19.0 * The SQLITE_READ authorizer callback is invoked once with a column name that is an empty string for every table referenced in a query from which no columns are extracted. * When using an index on an expression, try to use expression values already available in the index, rather than loading the original columns and recomputing the expression. * Enhance the flattening optimization so that it is able to flatten views on the right-hand side of a LEFT JOIN. * Use replace() instead of char() for escaping newline and carriage-return characters embedded in strings in the .dump output from the command-line shell. * Avoid unnecessary foreign key processing in UPDATE statements that do not touch the columns that are constrained by the foreign keys. * On a DISTINCT query that uses an index, try to skip ahead to the next distinct entry using the index rather than stepping through rows, when an appropriate index is available. * Avoid unnecessary invalidation of sqlite3_blob handles when making changes to unrelated tables. * Transfer any terms of the HAVING clause that use only columns mentioned in the GROUP BY clause over to the WHERE clause for faster processing. * Reuse the same materialization of a VIEW if that VIEW
Comments 0