🚧 wip database schema - #6
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| CREATE TABLE `incidentUpdate` ( | ||
| `id` int AUTO_INCREMENT PRIMARY KEY NOT NULL, | ||
| `incident_date` datetime, | ||
| `title` varchar(256), | ||
| `message` text, | ||
| `incident_id` int NOT NULL, | ||
| `created_at` timestamp NOT NULL DEFAULT (now()), | ||
| `updated_at` timestamp NOT NULL ON UPDATE CURRENT_TIMESTAMP); |
There was a problem hiding this comment.
What is the purpose of the table?
We will have to store every single change of an incident. Could be interesting to use tinybird for that.
There was a problem hiding this comment.
An incident in my mind was a set message you post when your service is down!
and the message is this table, an update to an incident
|
|
||
| workspaceId: int("workspace_id").notNull(), | ||
|
|
||
| slug: varchar("slug", { length: 256 }), // which is used for https://slug.openstatus.dev |
There was a problem hiding this comment.
We should store the slug inside a workspace. So that every company has only a single status page with all the websites.
There was a problem hiding this comment.
I thought we could have multiple page for a workspace :)
| import { relations } from "drizzle-orm"; | ||
| import { page } from "./page"; | ||
|
|
||
| export const statusJob = mysqlTable("statusJob", { |
There was a problem hiding this comment.
Hearing the name "status job" for the first time. Should we call it "ping"? I have something similar where I called it function monitor, but all are related to pinning a website.
There was a problem hiding this comment.
yep monitor makes sense!
* 🚧 wip database schema * 🚧 wip database schema * 🚧 wip database schema * 🚧 wip database schema * 🗃️update database
2 participants
No description provided.