-- schema.sql

-- Schema for pit in python / SQLite mode
-- v0.1

CREATE TABLE project (
    id              integer primary key,
    username        text, -- User the project belongs to.
    name            text, -- Project name.
    status          text, -- Project status.
    --number_of_tasks integer,  -- Number of tasks for the project.
    created_at      date, -- When the project was created?
    updatet_at      date  -- When the project was last updated?
);

CREATE TABLE task (
    id              integer primary key, -- TODO When delete, counter go down ==> problem?? Use autoincrement?
    project_id      integer,  -- Which project the task belongs to?
    username        text, -- User the task belongs to.
    name            text, -- Task name.
    status          text, -- Task status.
    priority        text, -- Task priority.
    date            date, -- Generic date/time, ex: task deadline.
    time            date, -- Generic time, ex: time spent on the task.
    -- number_of_notes integer,  -- Number of notes for the task.
    created_at      date, -- When the task was created?
    updated_at      date  -- When the task was last updated?
);

-- CREATE TRIGGER insert_task AFTER INSERT ON task
-- BEGIN
--     UPDATE project SET number_of_tasks = (SELECT count(*) FROM task WHERE project_id = new.project_id) WHERE id = new.project_id;
-- END;

-- CREATE TRIGGER delete_task AFTER DELETE ON task
-- BEGIN
--     UPDATE project SET number_of_tasks = (SELECT count(*) FROM task WHERE project_id = old.project_id) WHERE id = old.project_id;
-- END;

CREATE TABLE note (
    id         integer primary key,
    project_id integer,  -- Project the note belongs to (0 if belongs to task).
    task_id    integer,  -- Task the note belongs to (0 if belongs to project).
    username   text, -- User who created the note.
    message    text, -- The body of the note.
    created_at date, -- When the note was created?
    updated_at date  -- When the note was last updated?
);

CREATE TABLE action (
    id         integer primary key,
    project_id integer,  -- Project id (always set).
    task_id    integer,  -- Task id (set for task or note related actions).
    note_id    integer,  -- Note id (set for note related actions only).
    username   text, -- Who added the log message?
    action     text, -- What type of action ? (updated, created, etc.)
    message    text, -- Log message.
    created_at date  -- When log message was added?
);

CREATE TRIGGER action_insert_created_at AFTER INSERT ON action
BEGIN
    UPDATE action SET created_at = strftime('%Y-%m-%d %H:%M:%S.%s', 'now', 'localtime') WHERE id = new.id;
END;

CREATE TABLE current (
    id         integer,
    project_id integer,
    task_id    integer,
    note_id    integer
);

INSERT INTO current VALUES (0,0,0,0);
-- Trigger after insert for current values
CREATE TRIGGER current_project AFTER INSERT ON project
BEGIN
    UPDATE current SET project_id = new.id WHERE id = 0;
END;

CREATE TRIGGER current_task AFTER INSERT ON task
BEGIN
    UPDATE current SET task_id = new.id WHERE id = 0;
END;

CREATE TRIGGER current_note AFTER INSERT ON note
BEGIN
    UPDATE current SET note_id = new.id WHERE id = 0;
END;

-- Trigger after update for current values
CREATE TRIGGER update_project AFTER UPDATE ON project
BEGIN
    UPDATE current SET project_id = new.id WHERE id = 0;
END;

CREATE TRIGGER update_task AFTER UPDATE ON task
BEGIN
    UPDATE current SET task_id = new.id WHERE id = 0;
END;

CREATE TRIGGER update_note AFTER UPDATE ON note
BEGIN
    UPDATE current SET note_id = new.id WHERE id = 0;
END;