Bureaucrats, cc_docs_admin, cc_staff
2,318
edits
SQLite: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
[https://www.sqlite.org SQLite] is a "pocket database", in that it is a full-featured relational database which however dispenses with the client/server architecture of most such databases and instead exists entirely in a single diskfile. Software in a wide variety of common languages can read from and write to this database file using standard [https://en.wikipedia.org/wiki/SQL SQL] queries using the language's standard API for database interactions, assuming one exists and the database can be transferred to another computer simply by copying the file there. | [https://www.sqlite.org SQLite] is a "pocket database", in that it is a full-featured relational database which however dispenses with the client/server architecture of most such databases and instead exists entirely in a single diskfile. Software in a wide variety of common languages can read from and write to this database file using standard [https://en.wikipedia.org/wiki/SQL SQL] queries using the language's standard API for database interactions, assuming one exists and the database can be transferred to another computer simply by copying the file there. | ||
Like other databases, SQLite should not be used, particularly when it is being written to, on a shared filesystem such as home, scratch and project. Typically, you should copy your SQLite file to the local scratch <tt>$SLURM_TMPDIR</tt> at the beginning of a job, where you can then use the database without any issues and also enjoy the best possible performance. Note as well that SQLite is not intended for use with multiple threads or processes writing concurrently to the database; for this you should consider a [[Database_servers | client/server solution]]. | |||
==Using SQLite directly== | ==Using SQLite directly== | ||