Removed unnecesary bloat

This commit is contained in:
cdricms
2025-01-14 15:16:05 +01:00
parent 77fe6a5fab
commit e625c6740a
5 changed files with 0 additions and 58 deletions

View File

@@ -1,25 +0,0 @@
Latosa-escrima-db
- user (cedric job)
- planning_events
- event_id uuid PK,
- creation_date id,
- schedule_start date,
- schedule_end end,
- status { 'Canceled', 'Active', '' }
CHECK schedule_start < schedule_end
- events_to_users
- event_id uuid references planning_events(event_id),
- user_id uuid references user(user_id)
- blog
uuid: slug PK,
slug: string unique,
content: string,
label: string,
author: uuid references user_id,
published: string,
summary: string,
image: string,
href: string
- website settings
- auto accept demand ? true/false

View File

@@ -1,12 +0,0 @@
CREATE TABLE blogs (
uuid UUID PRIMARY KEY, -- The blog primary key
slug VARCHAR(255) UNIQUE NOT NULL, -- Slug must be unique and non-null
content TEXT NOT NULL, -- Content cannot be null
label VARCHAR(100), -- Optional label
author UUID REFERENCES users(user_id) ON DELETE SET NULL, -- Foreign key to user with cascading null for author deletion
published TIMESTAMP DEFAULT CURRENT_TIMESTAMP, -- Automatically set the published time
summary VARCHAR(500), -- A brief summary of the blog
image VARCHAR(255), -- URL for the blog image
href VARCHAR(255), -- Link to the blog if external
CONSTRAINT check_slug_length CHECK (length(slug) > 0) -- Ensure slug is not empty
);

View File

@@ -1,11 +0,0 @@
CREATE EXTENSION IF NOT EXISTS pgcrypto;
CREATE TYPE Event_status as ENUM('Canceled', 'Active')
CREATE TABLE events (
event_id UUID PRIMARY KEY, -- Use UUID as the primary key
creation_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP, -- Automatically capture the creation date
schedule_start DATE NOT NULL,
schedule_end DATE NOT NULL,
status Event_status DEFAULT 'Active', -- enum-like constraint for status
CHECK (schedule_start < schedule_end) -- Ensure the start date is before the end date
);

View File

@@ -1,6 +0,0 @@
CREATE TABLE events_to_users (
event_id UUID REFERENCES events(event_id) ON DELETE CASCADE, -- Foreign key with cascading delete for referential integrity
user_id UUID REFERENCES users(user_id) ON DELETE CASCADE, -- Foreign key with cascading delete
PRIMARY KEY (event_id, user_id) -- Ensure uniqueness of event-user pairs
);

View File

@@ -1,4 +0,0 @@
CREATE TABLE website_settings (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(), -- Auto-generate UUID for settings table
auto_accept_demand BOOLEAN DEFAULT FALSE -- Automatically accept demands by default is false
);