You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems it occurred with recent taxadb, but the databases are created in WAL mode. Hence, there is no way to open them if they are located in a read-only directory.
example:
$ sqlite3 taxadb_gb.sqlite
SQLite version 3.13.0 2016-05-18 10:57:30
Enter ".help"for usage hints.
sqlite> .schema
Error: unable to open database file
sqlite>
$ chmod +w .
$ sqlite3 taxadb_gb.sqlite
SQLite version 3.13.0 2016-05-18 10:57:30
Enter ".help"for usage hints.
sqlite> .schema
CREATE TABLE "taxa" ("ncbi_taxid" INTEGER NOT NULL PRIMARY KEY, "parent_taxid" INTEGER NOT NULL, "tax_name" VARCHAR(255) NOT NULL, "lineage_level" VARCHAR(255) NOT NULL);
CREATE TABLE "accession" ("id" INTEGER NOT NULL PRIMARY KEY, "taxid_id" INTEGER NOT NULL, "accession" VARCHAR(255) NOT NULL, FOREIGN KEY ("taxid_id") REFERENCES "taxa" ("ncbi_taxid"));
CREATE INDEX "accession_taxid_id" ON "accession" ("taxid_id");
CREATE UNIQUE INDEX "accession_accession" ON "accession" ("accession");
i have to delete the embedded journal in write mode:
PRAGMA journal_mode=DELETE;
$ chmod -w .
$ sqlite3 taxadb_gb.sqlite
SQLite version 3.13.0 2016-05-18 10:57:30
Enter ".help"for usage hints.
sqlite> .schema
CREATE TABLE "taxa" ("ncbi_taxid" INTEGER NOT NULL PRIMARY KEY, "parent_taxid" INTEGER NOT NULL, "tax_name" VARCHAR(255) NOT NULL, "lineage_level" VARCHAR(255) NOT NULL);
CREATE TABLE "accession" ("id" INTEGER NOT NULL PRIMARY KEY, "taxid_id" INTEGER NOT NULL, "accession" VARCHAR(255) NOT NULL, FOREIGN KEY ("taxid_id") REFERENCES "taxa" ("ncbi_taxid"));
CREATE INDEX "accession_taxid_id" ON "accession" ("taxid_id");
CREATE UNIQUE INDEX "accession_accession" ON "accession" ("accession");
sqlite>
I think, according to the regular usage of a taxadb database (read-only), the WAL mode should not be used.
Hi,
It seems it occurred with recent taxadb, but the databases are created in
WAL
mode. Hence, there is no way to open them if they are located in a read-only directory.example:
i have to delete the embedded journal in write mode:
I think, according to the regular usage of a taxadb database (read-only), the WAL mode should not be used.
Reference:
https://www.sqlite.org/wal.html#readonly
The text was updated successfully, but these errors were encountered: