1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
|
+
+
+
+
+
|
<h1>Fossil Database Schemas</h1>
The Fossil DB schemas can be perused, in the form of
commented SQL, in [http://fossil.wanderinghorse.net/repos/libfossil/doxygen/|the API docs].
The library reserves the db symbol prefixes "fsl_" and "fx_fsl_" (case-insensitive) for its own use - clients should not define any functions or tables with those name prefixes. Fossil(1) reserves <em>all</em> table names which do not start with "fx_" ("fossil extension"). During a rebuild, fossil(1) will <em>drop</em> any repo tables it does not know about unless their names start with "fx_".
<h1>Fossil DB User-defined Functions</h1>
A fossil-bound DB handle gets a few extra SQL-callable functions, as
listed below in alphabetical order...
<h3>FSL_CKOUT_DIR()</h3>
<tt>FSL_CKOUT_DIR([INTEGER=0])</tt> returns the path to the current checkout directory, or NULL if no checkout is opened. If passed no argument or passed a truthy value, the trailing slash is included in the returned value. If passed a falsy argument, the slash is not included.
<h3>FSL_CI_MTIME()</h3>
<tt>FSL_CI_MTIME(INT,INT)</tt> takes two RIDs as arguments: the manifest (checkin) version RID and the blob.rid value of a file which part of the first RID's checkin.
It behaves like <tt>fsl_mtime_of_manifest_file()</tt>, returning the calculated (and highly synthetic!) mtime as an SQL integer (Unix epoch timestamp). This is primarily
for internal use.
|