Compare commits
1
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
452e3778ac |
@@ -941,16 +941,16 @@ Only one `scan` at a time can hold the lock.
|
|||||||
|
|
||||||
#### Schema
|
#### Schema
|
||||||
|
|
||||||
The schema is the database's layout: its tables, its index and its triggers.
|
The schema is the database's layout, its table and its index.
|
||||||
`PRAGMA user_version` holds the schema version, currently 1. An empty database
|
`PRAGMA user_version` holds the schema version, currently 1. An empty database
|
||||||
is at version 0, and `scan` sets it up. Any other version is a fatal error.
|
is at version 0, and `scan` sets it up. Any other version is a fatal error.
|
||||||
`report`, `trees` and `info` set nothing up, so for them version 0 is a fatal
|
`report`, `trees` and `info` set nothing up, so for them version 0 is a fatal
|
||||||
error too. `scan` creates the tables, the index and the triggers and sets the
|
error too. `scan` creates the table and the index and sets the version in one
|
||||||
version in one transaction (see "`info` mode"). So they all land together or not
|
transaction (see "`info` mode"). So the three land together or not at all. A
|
||||||
at all. A first scan stopped while doing so leaves an empty database, which the
|
first scan stopped while doing so leaves an empty database, which the next scan
|
||||||
next scan sets up. A database at version 0 that already has a `files` table was
|
sets up. A database at version 0 that already has a `files` table was not made
|
||||||
not made by `sfdupes`. Every subcommand refuses it, with an error telling you to
|
by `sfdupes`. Every subcommand refuses it, with an error telling you to remove
|
||||||
remove the file and rescan.
|
the file and rescan.
|
||||||
|
|
||||||
```sql
|
```sql
|
||||||
CREATE TABLE files (
|
CREATE TABLE files (
|
||||||
|
|||||||
Reference in new issue
Block a user