moves recording BLOB from table movement to table is_able_to_play, so that recordings can be stored per user, not per movement

This commit is contained in:
2023-11-09 09:40:10 +01:00
parent 69d701d600
commit 7352af038b
2 changed files with 2 additions and 2 deletions

View File

@@ -180,7 +180,7 @@ class work_under_id:
saetze = dict()
nummern = set()
suw_liste = self.reader.execute(sql_suw).fetchall()
# 0 work_id, 1 mov_number, 2 numb, 3 designation, 4 mus_key, 5 recording
# 0 work_id, 1 mov_number, 2 numb, 3 designation, 4 mus_key
for satz in suw_liste:
saetze[satz[1]] = satz[2], satz[3], satz[4]
if not satz[2] is None:

View File

@@ -27,7 +27,6 @@ CREATE TABLE movement (
numb VARCHAR(15),
designation VARCHAR(63),
mus_key VARCHAR(15),
recording BLOB,
PRIMARY KEY(work_id, mov_number),
FOREIGN KEY(work_id) REFERENCES work(id)
);
@@ -50,6 +49,7 @@ CREATE TABLE is_able_to_play(
mov_id INTEGER NOT NULL,
pianist_id INTEGER NOT NULL,
days_to_practice INTEGER DEFAULT 7,
recording BLOB,
PRIMARY KEY(work_id, mov_id, pianist_id),
FOREIGN KEY(work_id, mov_id) REFERENCES movement(work_id, mov_number),
FOREIGN KEY(pianist_id) REFERENCES pianist(id)