[tracker/tracker-0.16] man-pages: Added information about TRACKER_SPARQL_BACKEND and TRACKER_PRAGMAS_FILE

[Martyn James Russell <mr src gnome org>]

commit 1d7d14a19f84b3865cb2ac1fcc7bbf625c5cd62d
Author: Martyn Russell <martyn lanedo com>
Date:   Tue Oct 8 20:56:57 2013 +0100

    man-pages: Added information about TRACKER_SPARQL_BACKEND and TRACKER_PRAGMAS_FILE
    
    To tracker-info, tracker-search, tracker-sparql and tracker-tag - where it's
    useful.

 docs/manpages/tracker-info.1   |   27 +++++++++++++++++++++++++++
 docs/manpages/tracker-search.1 |   27 +++++++++++++++++++++++++++
 docs/manpages/tracker-sparql.1 |   26 ++++++++++++++++++++++++++
 docs/manpages/tracker-tag.1    |   26 ++++++++++++++++++++++++++
 4 files changed, 106 insertions(+), 0 deletions(-)
---
diff --git a/docs/manpages/tracker-info.1 b/docs/manpages/tracker-info.1
index 48fd819..db68cfb 100644
--- a/docs/manpages/tracker-info.1
+++ b/docs/manpages/tracker-info.1
@@ -44,6 +44,33 @@ Output results as Turtle RDF. If \-f is enabled, full URIs are shown
 for subjects, predicates and objects; otherwise, shortened URIs are
 used, and all the prefixes Tracker knows about are printed at the top
 of the output.
+
+.SH ENVIRONMENT
+.TP
+.B TRACKER_SPARQL_BACKEND
+This option allows you to choose which backend you use for connecting
+to the database. This choice can limit your functionality. There are
+three settings.
+
+With "\fBdirect\fR" the connection to the database is made directly to
+the file itself on the disk, there is no intermediary daemon or
+process. The "\fBdirect\fR" approach is purely \fIread-only\fR.
+
+With "\fBbus\fR" the \fBtracker-store\fR process is used to liase with
+the database queuing all requests and managing the connections via an
+IPC / D-Bus. This adds a small overhead \fIBUT\fR this is the only
+approach you can use if you want to \fIwrite\fR to the database.
+
+With "\fBauto\fR" the backend is decided for you, much like it would
+be if this environment variable was undefined.
+
+.TP
+.B TRACKER_PRAGMAS_FILE
+Tracker has a fixed set of PRAGMA settings for creating its SQLite connection.
+With this environment variable pointing to a text file you can override these
+settings. The file is a \\n separated list of SQLite queries to execute on any
+newly created SQLite connection in tracker-store.
+
 .SH SEE ALSO
 .BR tracker-store (1),
 .BR tracker-sparql (1).
diff --git a/docs/manpages/tracker-search.1 b/docs/manpages/tracker-search.1
index 1e76fdd..d0b6604 100644
--- a/docs/manpages/tracker-search.1
+++ b/docs/manpages/tracker-search.1
@@ -19,6 +19,7 @@ for example) then ALL items in that category are returned instead.
 \fIEXPRESSION\fR
 One or more terms to search. The default operation is a logical AND.
 For logical OR operations, see -r.
+
 .SH OPTIONS
 .TP
 .B \-?, \-\-help-all
@@ -118,6 +119,32 @@ titles and links for each bookmark found.
 .B \-V, \-\-version
 Print version.
 
+.SH ENVIRONMENT
+.TP
+.B TRACKER_SPARQL_BACKEND
+This option allows you to choose which backend you use for connecting
+to the database. This choice can limit your functionality. There are
+three settings.
+
+With "\fBdirect\fR" the connection to the database is made directly to
+the file itself on the disk, there is no intermediary daemon or
+process. The "\fBdirect\fR" approach is purely \fIread-only\fR.
+
+With "\fBbus\fR" the \fBtracker-store\fR process is used to liase with
+the database queuing all requests and managing the connections via an
+IPC / D-Bus. This adds a small overhead \fIBUT\fR this is the only
+approach you can use if you want to \fIwrite\fR to the database.
+
+With "\fBauto\fR" the backend is decided for you, much like it would
+be if this environment variable was undefined.
+
+.TP
+.B TRACKER_PRAGMAS_FILE
+Tracker has a fixed set of PRAGMA settings for creating its SQLite connection.
+With this environment variable pointing to a text file you can override these
+settings. The file is a \\n separated list of SQLite queries to execute on any
+newly created SQLite connection in tracker-store.
+
 .SH SEE ALSO
 .BR tracker-store (1),
 .BR tracker-stats (1),
diff --git a/docs/manpages/tracker-sparql.1 b/docs/manpages/tracker-sparql.1
index 7b0f6f1..09b6045 100644
--- a/docs/manpages/tracker-sparql.1
+++ b/docs/manpages/tracker-sparql.1
@@ -109,6 +109,32 @@ Properties: 4
 .B \-V, \-\-version
 Print version.
 
+.SH ENVIRONMENT
+.TP
+.B TRACKER_SPARQL_BACKEND
+This option allows you to choose which backend you use for connecting
+to the database. This choice can limit your functionality. There are
+three settings.
+
+With "\fBdirect\fR" the connection to the database is made directly to
+the file itself on the disk, there is no intermediary daemon or
+process. The "\fBdirect\fR" approach is purely \fIread-only\fR.
+
+With "\fBbus\fR" the \fBtracker-store\fR process is used to liase with
+the database queuing all requests and managing the connections via an
+IPC / D-Bus. This adds a small overhead \fIBUT\fR this is the only
+approach you can use if you want to \fIwrite\fR to the database.
+
+With "\fBauto\fR" the backend is decided for you, much like it would
+be if this environment variable was undefined.
+
+.TP
+.B TRACKER_PRAGMAS_FILE
+Tracker has a fixed set of PRAGMA settings for creating its SQLite connection.
+With this environment variable pointing to a text file you can override these
+settings. The file is a \\n separated list of SQLite queries to execute on any
+newly created SQLite connection in tracker-store.
+
 .SH EXAMPLES
 .TP
 List all classes
diff --git a/docs/manpages/tracker-tag.1 b/docs/manpages/tracker-tag.1
index b5756ac..73519a4 100644
--- a/docs/manpages/tracker-tag.1
+++ b/docs/manpages/tracker-tag.1
@@ -73,6 +73,32 @@ and provides a description to go with the tag label according to
 .B \-V, \-\-version
 Print version.
 
+.SH ENVIRONMENT
+.TP
+.B TRACKER_SPARQL_BACKEND
+This option allows you to choose which backend you use for connecting
+to the database. This choice can limit your functionality. There are
+three settings.
+
+With "\fBdirect\fR" the connection to the database is made directly to
+the file itself on the disk, there is no intermediary daemon or
+process. The "\fBdirect\fR" approach is purely \fIread-only\fR.
+
+With "\fBbus\fR" the \fBtracker-store\fR process is used to liase with
+the database queuing all requests and managing the connections via an
+IPC / D-Bus. This adds a small overhead \fIBUT\fR this is the only
+approach you can use if you want to \fIwrite\fR to the database.
+
+With "\fBauto\fR" the backend is decided for you, much like it would
+be if this environment variable was undefined.
+
+.TP
+.B TRACKER_PRAGMAS_FILE
+Tracker has a fixed set of PRAGMA settings for creating its SQLite connection.
+With this environment variable pointing to a text file you can override these
+settings. The file is a \\n separated list of SQLite queries to execute on any
+newly created SQLite connection in tracker-store.
+
 .SH SEE ALSO
 .BR tracker-store (1),
 .BR tracker-sparql (1),