changes recording datatype from BLOB to VARCHAR, as I made up my mind and think, that storing the recordings as files somewhere is better than putting them in the database. recording should point to the path where the file can be found. (Maybe is copied and renamed to a nice place within the userspace)

README.md

@@ -22,7 +22,7 @@ At the moment, an alpha version is undertaken, with these features:
 - Show movements through works (`sw work_number`)
 - Mark movement as mastered for active user (`m number_of_work number_of_movement`)
 - Show possible commands (`h`)
-- (planned) Show mastered movements for activated user
+- Show mastered movements for activated user (`sm`)
 - (planned) display, if work or movement is mastered from active user when viewing works and movements
 - (planned) Save recordings per movement in db
 - (planned) Listen to saved recordings

repertoire.sql

@@ -49,7 +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,
+    recording VARCHAR(255),
     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)