Oops--CSL table needs to be defined in scrapers.sql too.

(The problem with the current system is that any local translators or styles will be wiped out on upgrades (though not auto-updates), but the solution for that is probably to just offer an SQL file that the user can put custom SQL statements in to be run on upgrades (sorta the same idea as user.js in Firefox). Will deal with that at a later date, though.)
This commit is contained in:
Dan Stillman 2006-10-02 21:25:47 +00:00
parent 0246e79538
commit eccc2159c1
2 changed files with 11 additions and 9 deletions

View file

@ -1,4 +1,4 @@
-- 93
-- 94
DROP TABLE IF EXISTS translators;
CREATE TABLE translators (
@ -16,6 +16,16 @@ CREATE TABLE translators (
DROP INDEX IF EXISTS translators_type;
CREATE INDEX translators_type ON translators(translatorType);
DROP TABLE IF EXISTS csl;
CREATE TABLE csl (
cslID TEXT PRIMARY KEY,
updated DATETIME,
title TEXT,
csl TEXT
);
-- Set the following timestamp to the most recent scraper update date
REPLACE INTO "version" VALUES ('repository', STRFTIME('%s', '2006-10-01 17:00:00'));

View file

@ -102,14 +102,6 @@
FOREIGN KEY (transactionID) REFERENCES transactions(transactionID)
);
DROP TABLE IF EXISTS csl;
CREATE TABLE csl (
cslID TEXT PRIMARY KEY,
updated DATETIME,
title TEXT,
csl TEXT
);
INSERT INTO "fieldFormats" VALUES(1, '.*', 0);
INSERT INTO "fieldFormats" VALUES(2, '[0-9]*', 1);