schedule

Tables (5)

comments (댓글)

  • id (PK) — BIGINT — Primary key — NOT NULL
  • user_id (FK) — BIGINT — Foreign key → users.id — NOT NULL
  • post_id (FK2) — BIGINT — Foreign key → posts.user_id — NOT NULL
  • contents (Field) — VARCHAR — NOT NULL
  • created_at (Field3) — DATETIME
  • modified_at (Field4) — DATETIME

followers (팔로워)

  • id (PK) — BIGINT — Primary key — NOT NULL
  • user_id (FK) — BIGINT — Foreign key → users.id — NOT NULL

followings (팔로잉)

  • id (PK) — BIGINT — Primary key — NOT NULL
  • user_id (FK) — BIGINT — Foreign key → users.id — NOT NULL

posts (게시글)

  • id (PK) — BIGINT — Primary key — NOT NULL
  • user_id (FK) — BIGINT — Foreign key → users.id — NOT NULL
  • photo (Field) — VARCHAR — NOT NULL
  • contents (Field2) — VARCHAR
  • created_at (Field3) — DATETIME
  • modified_at (Field4) — DATETIME

users (회원)

  • id (PK) — BIGINT — Primary key — NOT NULL
  • nickname (Field) — VARCHAR
  • email (Field2) — VARCHAR
  • password (Field3) — VARCHAR
  • status_message (Field4) — VARCHAR
  • created_at (Field5) — DATETIME
  • modified_at (Field6) — DATETIME
  • deleted_at (Field7) — DATETIME