Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
en:guides:database [2013/04/30 22:06] linea |
en:guides:database [2014/11/08 18:34] emgi [Keeping sqlite up-to-date] |
||
|---|---|---|---|
| Line 33: | Line 33: | ||
| Please note that the file does not shrink when a large amount of data is deleted. Instead, the empty space is preserved and re-used before the file starts to increase in size again. | Please note that the file does not shrink when a large amount of data is deleted. Instead, the empty space is preserved and re-used before the file starts to increase in size again. | ||
| Something else to keep in mind is that the file permissions must be set correctly to be able read or write the database. | Something else to keep in mind is that the file permissions must be set correctly to be able read or write the database. | ||
| + | |||
| + | ======Keeping sqlite up-to-date====== | ||
| + | SQLite is still under development and new versions are made available every one-two months. You can run the latest client without compiling and installing a package every time. In the end, it is just one binary file: sqlite3. This file is available as a precompiled binary for download from www.sqlite.org. All that's needed is to move it to the correct folder, thereby replacing the old version. A sample script to automate this action could look like this: | ||
| + | <code>cd /home/<your-home-dir> | ||
| + | if [ -s sqlite3 ]; then | ||
| + | rm sqlite3.old | ||
| + | mv /usr/bin/sqlite3 sqlite3.old | ||
| + | mv sqlite3 /usr/bin/ | ||
| + | chmod 755 /usr/bin/sqlite3 | ||
| + | fi | ||
| + | </code> | ||
| + | This script looks for a file named sqlite3 in /home/<your-home-dir>, if found it moves the old sqlite3 binary to sqlite3.old in /home/<your-home-dir> and installs the latest version with the correct access mode in /usr/bin. | ||
| + | |||