yonlu
75b2a349eb
On existing databases, CREATE TABLE IF NOT EXISTS audio_files is a no-op but the standalone CREATE INDEX on library_id would fail because the column doesn't exist until migration 6 runs. The migration already creates this index, so removing it from the schema file is correct.
25 lines
933 B
SQL
25 lines
933 B
SQL
CREATE TABLE IF NOT EXISTS audio_files (
|
|
id integer PRIMARY KEY,
|
|
file_path text NOT NULL UNIQUE,
|
|
length_milliseconds int NOT NULL,
|
|
file_type_id int NOT NULL,
|
|
recording_id int NOT NULL,
|
|
sample_rate int NOT NULL DEFAULT 0,
|
|
bit_depth int NOT NULL DEFAULT 0,
|
|
channels int NOT NULL DEFAULT 0,
|
|
bitrate int NOT NULL DEFAULT 0,
|
|
file_size int NOT NULL DEFAULT 0,
|
|
basename text NOT NULL DEFAULT '',
|
|
library_id int NOT NULL DEFAULT 0,
|
|
FOREIGN KEY(file_type_id) REFERENCES file_types(id),
|
|
FOREIGN KEY(recording_id) REFERENCES recordings(id),
|
|
FOREIGN KEY(library_id) REFERENCES libraries(id)
|
|
);
|
|
|
|
CREATE INDEX IF NOT EXISTS idx_audio_files_recording_id
|
|
ON audio_files(recording_id);
|
|
|
|
-- idx_audio_files_library_id is created by migration 6 (not here) because
|
|
-- on existing databases this schema file is a no-op (CREATE TABLE IF NOT EXISTS)
|
|
-- and the library_id column doesn't exist until the migration adds it.
|