diff -r 418e11eb6fea -r 192b0059a6c4 relpipe-data/examples-in-sql-selecting-existing-database.xml --- a/relpipe-data/examples-in-sql-selecting-existing-database.xml Thu May 21 01:23:23 2020 +0200 +++ b/relpipe-data/examples-in-sql-selecting-existing-database.xml Sat Jun 06 01:57:24 2020 +0200 @@ -10,16 +10,16 @@
Both the relpipe-tr-sql
and relpipe-in-sql
- support the option --file
and can store data in a file instead of just in-memory.
- Primary purpose of this option is to offload to HDD and be able to process more data whithout consuming too much RAM.
- So such file is usually a temporary one and is deleted immediately after the transformation.
- But we can also direct it to an existing file and append new relations to it.
- Or we can create a new file and do not delete it – using the --file-keep true
option.
+ support options --data-source-name
and --data-source-string
+ that can be used for connecting to a different database than the in-memory SQLite one.
+ This is useful if we want to offload to HDD and be able to process more data whithout consuming too much RAM.
+ Or if we want to access an existing database instead of just transforming records from the STDIN to STDOUT.
+ These options allow connecting to any DBMS.
Thus we can use the relpipe-in-sql
as a database client to access existing SQLite files and SELECT from them (and then convert the results to any supported format).
- An we can use the relpipe-tr-sql
as an output filter which converts relational data to a SQLite file that can be queried later.
+ And we can use the relpipe-tr-sql
as an output filter which converts relational data to a SQLite file that can be queried later.
@@ -35,11 +35,11 @@
- We can then query it using sqlite.fossil
using