manual: document that CSV is colon-separated.
Traditionally, CSV has meant comma-separated values, but in the context of newfol, it always means colon-separated. Document this. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
This commit is contained in:
parent
9611bf42df
commit
358efbab51
1 changed files with 2 additions and 2 deletions
|
|
@ -30,8 +30,8 @@ intended behavior of the database. Refer to <<_schema_file>> for a description
|
||||||
of the contents of this file. It is the only file which may be hand-edited.
|
of the contents of this file. It is the only file which may be hand-edited.
|
||||||
|
|
||||||
Each database also contains a `dtb` file, which contains the actual data. This
|
Each database also contains a `dtb` file, which contains the actual data. This
|
||||||
will be in CSV, pickle, or JSON format, depending on the contents of the
|
will be in CSV (colon-separated values), pickle, or JSON format, depending on
|
||||||
`version` file. It may also be compressed.
|
the contents of the `version` file. It may also be compressed.
|
||||||
|
|
||||||
The `dtb.checksum` file provides a cryptographic SHA-2 hash and length to ensure
|
The `dtb.checksum` file provides a cryptographic SHA-2 hash and length to ensure
|
||||||
that the data has not been accidentally corrupted. newfol will not open a
|
that the data has not been accidentally corrupted. newfol will not open a
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue