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:Backports:SLE-15-SP4:FactoryCandidates/sqlite3 && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
baselibs.conf | 0000000105 105 Bytes | |
sqlite-autoconf-3110100.tar.gz | 0002359545 2.25 MB | |
sqlite-doc-3110100.zip | 0005386958 5.14 MB | |
sqlite-fts5-link.patch | 0000000437 437 Bytes | |
sqlite3-link-binary-with-libsqlite3.patch | 0000000701 701 Bytes | |
sqlite3.changes | 0000087092 85.1 KB | |
sqlite3.spec | 0000005264 5.14 KB |
Revision 83 (latest revision is 153)
Dominique Leuenberger (dimstar_suse)
accepted
request 367794
from
Ismail Dönmez (namtrac)
(revision 83)
- Fix sqlite-fts5-link.patch: link libsqlite3.so with libm instead of the sqlite3 binary: the library is the actual user of log(). - Add sqlite3-link-binary-with-libsqlite3.patch: dyamically link /usr/bin/sqlite3 to libsqlite3 instead of statically using it. - Move autoreconf call to build section, where it belongs. - Enable FTS5 support. - Add sqlite-fts5-link.patch to link to math library because FTS5 code uses log(). - SQLite 3.11.1: * Fix an FTS5 issue in which the 'optimize' command could cause index corruption. * Fix a buffer overread that might occur if FTS5 is used to query a corrupt database file. * Increase the maximum "scope" value for the spellfix1 extension from 6 to 30. - explicitly enable readline support - run spec-cleaner
Comments 0