initial commit

migrations/00000000000000_diesel_initial_setup/down.sql

@@ -0,0 +1,6 @@
+-- This file was automatically created by Diesel to setup helper functions
+-- and other internal bookkeeping. This file is safe to edit, any future
+-- changes will be added to existing projects as new migrations.
+
+DROP FUNCTION IF EXISTS diesel_manage_updated_at(_tbl regclass);
+DROP FUNCTION IF EXISTS diesel_set_updated_at();

migrations/00000000000000_diesel_initial_setup/up.sql

@@ -0,0 +1,36 @@
+-- This file was automatically created by Diesel to setup helper functions
+-- and other internal bookkeeping. This file is safe to edit, any future
+-- changes will be added to existing projects as new migrations.
+
+
+
+
+-- Sets up a trigger for the given table to automatically set a column called
+-- `updated_at` whenever the row is modified (unless `updated_at` was included
+-- in the modified columns)
+--
+-- # Example
+--
+-- ```sql
+-- CREATE TABLE users (id SERIAL PRIMARY KEY, updated_at TIMESTAMP NOT NULL DEFAULT NOW());
+--
+-- SELECT diesel_manage_updated_at('users');
+-- ```
+CREATE OR REPLACE FUNCTION diesel_manage_updated_at(_tbl regclass) RETURNS VOID AS $$
+BEGIN
+    EXECUTE format('CREATE TRIGGER set_updated_at BEFORE UPDATE ON %s
+                    FOR EACH ROW EXECUTE PROCEDURE diesel_set_updated_at()', _tbl);
+END;
+$$ LANGUAGE plpgsql;
+
+CREATE OR REPLACE FUNCTION diesel_set_updated_at() RETURNS trigger AS $$
+BEGIN
+    IF (
+        NEW IS DISTINCT FROM OLD AND
+        NEW.updated_at IS NOT DISTINCT FROM OLD.updated_at
+    ) THEN
+        NEW.updated_at := current_timestamp;
+    END IF;
+    RETURN NEW;
+END;
+$$ LANGUAGE plpgsql;

migrations/2023-12-29-191547_users/down.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE users;

migrations/2023-12-29-191547_users/up.sql

@@ -0,0 +1,13 @@
+-- Your SQL goes here
+CREATE TABLE IF NOT EXISTS users
+(
+    id         VARCHAR(24) DEFAULT nanoid(24),
+    name       VARCHAR(255)              NOT NULL,
+    email      VARCHAR(255)              NOT NULL,
+    password   TEXT                      NOT NULL,
+
+    updated_at TIMESTAMP,
+    created_at TIMESTAMP   DEFAULT now() NOT NULL,
+
+    PRIMARY KEY (id)
+);

migrations/2023-12-30-162032_playlists/down.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE playlists;

migrations/2023-12-30-162032_playlists/up.sql

@@ -0,0 +1,16 @@
+CREATE TABLE IF NOT EXISTS playlists
+(
+    id         VARCHAR(24) DEFAULT nanoid(24),
+    name       VARCHAR(255)              NOT NULL,
+
+    creator_id VARCHAR(24)               NOT NULL,
+
+    created_at TIMESTAMP   DEFAULT now() NOT NULL,
+    updated_at TIMESTAMP,
+
+    PRIMARY KEY (id),
+    FOREIGN KEY (creator_id)
+        REFERENCES users (id)
+);
+
+CREATE INDEX ON playlists (creator_id);

migrations/2023-12-30-192105_tracks/down.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE tracks;

migrations/2023-12-30-192105_tracks/up.sql

@@ -0,0 +1,16 @@
+-- Your SQL goes here
+CREATE TABLE IF NOT EXISTS tracks
+(
+    id          VARCHAR(24)   DEFAULT nanoid(24),
+    title       VARCHAR(255) NOT NULL,
+    duration_ms INT  NOT NULL DEFAULT 0,
+
+    created_at  TIMESTAMP     DEFAULT now() NOT NULL,
+    updated_at  TIMESTAMP,
+
+--  music services
+    spotify_id  VARCHAR(21) UNIQUE,
+    tidal_id    VARCHAR(10) UNIQUE,
+
+    PRIMARY KEY (id)
+);

migrations/2023-12-30-214938_playlists_tracks/down.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE playlists_tracks;

migrations/2023-12-30-214938_playlists_tracks/up.sql

@@ -0,0 +1,5 @@
+CREATE TABLE IF NOT EXISTS playlists_tracks (
+    playlist_id VARCHAR(24) REFERENCES playlists(id),
+    track_id VARCHAR(24) REFERENCES tracks(id),
+    PRIMARY KEY (playlist_id, track_id)
+);