SQLite/fr: Difference between revisions

SQLite/fr (view source)

Revision as of 20:25, 11 March 2020

27 bytes added , 4 years ago

Created page with "[https://fr.wikipedia.org/wiki/SQLite] est un système de gestion de bases de données pour construire des BD dites ''de poche'', car elles offrent toutes les fonctionnalités..."

Diane27

rsnt_translations

56,437

edits

@@ Line 1: / Line 1: @@
 <languages />
-[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://fr.wikipedia.org/wiki/SQLite] est un système de gestion de bases de données pour construire des BD dites ''de poche'', car elles offrent toutes les fonctionnalités des BD relationnelles sans l'architecture client-serveur, avec en plus l'avantage que toutes les données résident sur un seul fichier disque qui peut simplement être copié sur un autre ordinateur. Des applications écrites dans plusieurs langages bien connus peuvent lire et écrire dans un fichier SQLite par des requêtes [https://en.wikipedia.org/wiki/SQL SQL] standard via leur API d'interaction avec les BD.
 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]].