jrmiller82
/
pathfinder-2-sqlite-MIRROR
mirror of https://gitlab.com/jrmiller82/pathfinder-2-sqlite.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

move feats schema to new feats.sql file

merge-requests/15/head
James Miller 2019-08-06 15:39:08 -05:00
parent a044b5ef93
commit a6f3b03d50
2 changed files with 22 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
schema/ancestries.sql
View File

@ -1,16 +1,13 @@
-- -*- mode:sql sql-product:sqlite -*- -- -*- mode:sql sql-product:sqlite -*-
/* /*
TODO Need to decide on whether to do a massive feats table, or to split feats TODO Need to decide on whether to do a massive feats table, or to split feats
into separate tables for general feats, ancestry feats, background feats, etc... into separate tables for general feats, ancestry feats, background feats, etc...
I think one big feat table that has a feat type in it and then an ancestry_feat I think one big feat table that has a feat type in it and then an ancestry_feat
table that matches feats to ancestries, etc.. table that matches feats to ancestries, etc..
*/ */
CREATE TABLE ancestries ( CREATE TABLE ancestries (
ancestry_id INTEGER PRIMARY KEY, ancestry_id INTEGER PRIMARY KEY,
short_name TEXT NOT NULL UNIQUE, short_name TEXT NOT NULL UNIQUE,
@ -80,8 +77,6 @@ CREATE TABLE ancestries_traits (
FOREIGN KEY (trait_id) REFERENCES traits(trait_id) FOREIGN KEY (trait_id) REFERENCES traits(trait_id)
); );
CREATE TABLE ancestries_langs ( CREATE TABLE ancestries_langs (
id INTEGER PRIMARY KEY, id INTEGER PRIMARY KEY,
ancestry_id INTEGER NOT NULL, ancestry_id INTEGER NOT NULL,
@ -89,7 +84,6 @@ CREATE TABLE ancestries_langs (
FOREIGN KEY (ancestry_id) REFERENCES ancestries(ancestry_id), FOREIGN KEY (ancestry_id) REFERENCES ancestries(ancestry_id),
FOREIGN KEY (lang_id) REFERENCES langs(lang_id)); FOREIGN KEY (lang_id) REFERENCES langs(lang_id));
CREATE TABLE ancestry_additionalangs ( CREATE TABLE ancestry_additionalangs (
id INTEGER PRIMARY KEY, id INTEGER PRIMARY KEY,
ancestry_id INTEGER NOT NULL, ancestry_id INTEGER NOT NULL,
@ -97,24 +91,3 @@ CREATE TABLE ancestry_additionalangs (
FOREIGN KEY (ancestry_id) REFERENCES ancestries(ancestry_id), FOREIGN KEY (ancestry_id) REFERENCES ancestries(ancestry_id),
FOREIGN KEY (lang_id) REFERENCES langs(lang_id) FOREIGN KEY (lang_id) REFERENCES langs(lang_id)
); );
/* Need to rethink how to model the various prerequisites */
CREATE TABLE feats (
feat_id INTEGER PRIMARY KEY,
short_name TEXT NOT NULL UNIQUE,
prereq_feats INTEGER,
prereq_ability_scores INTEGER,
prereq_proficiency_ranks INTEGER,
frequency TEXT,
triggers TEXT,
reqs TEXT
);
CREATE TABLE feats_traits (
id INTEGER PRIMARY KEY,
feat_id INTEGER NOT NULL,
trait_id INTEGER NOT NULL,
FOREIGN KEY (feat_id) REFERENCES feats(feat_id),
FOREIGN KEY (trait_id) REFERENCES traits(trait_id)
);

22
schema/feats.sql 100644
View File

@ -0,0 +1,22 @@
-- -*- mode:sql sql-product:sqlite -*-
/* Need to rethink how to model the various prerequisites */
CREATE TABLE feats (
feat_id INTEGER PRIMARY KEY,
short_name TEXT NOT NULL UNIQUE,
prereq_feats INTEGER,
prereq_ability_scores INTEGER,
prereq_proficiency_ranks INTEGER,
frequency TEXT,
triggers TEXT,
reqs TEXT
);
CREATE TABLE feats_traits (
id INTEGER PRIMARY KEY,
feat_id INTEGER NOT NULL,
trait_id INTEGER NOT NULL,
FOREIGN KEY (feat_id) REFERENCES feats(feat_id),
FOREIGN KEY (trait_id) REFERENCES traits(trait_id)
);