SALT_table

Tables (5)

main_category

  • Name (main_category_name) — VARCHAR(50) — Primary key — NOT NULL
  • Explanation (main_category_explanation) — TEXT

notice_post

  • id (notice_post_id) — iNT — Primary key — NOT NULL
  • id (user_id) — VARCHAR(100) — Foreign key → user.id — NOT NULL
  • Name (sub_category_name) — VARCHAR(50) — Foreign key → sub_category.Name — NOT NULL
  • Name (main_category_name) — VARCHAR(50) — Foreign key → sub_category.Name — NOT NULL
  • Title (notice_post_title) — VARCHAR(50) — NOT NULL
  • Contents (notice_post_contents) — TEXT — NOT NULL
  • create_day (notice_post_create_day) — DATETIME — NOT NULL
  • viewcount (post_viewcount) — INT — NOT NULL

post

  • id (post_id) — INT — Primary key — NOT NULL
  • id (user_id) — VARCHAR(100) — Foreign key → user.id — NOT NULL
  • Name (sub_category_name) — VARCHAR(50) — Foreign key → sub_category.Name — NOT NULL
  • Name (main_category_name) — VARCHAR(50) — Foreign key → sub_category.Name — NOT NULL
  • Title (post_title) — VARCHAR(100) — NOT NULL
  • Contents (post_contents) — TEXT — NOT NULL
  • Writer (post_writer) — VARCHAR(50) — NOT NULL — user와의 연결성이 집중되므로 FK가 아니라 그냥 그 유저의 현재 상태를 들고오는 식으로 해결
  • create_day (post_create_day) — DATETIME — NOT NULL
  • viewcount (post_viewcount) — INT

sub_category

  • Name (sub_category_name) — VARCHAR(50) — Primary key — NOT NULL
  • Name (main_category_name) — VARCHAR(50) — Foreign key → main_category.Name — NOT NULL
  • Explanation (sub_category_explanation) — VARCHAR(50)

user

  • id (user_id) — VARCHAR(100) — Primary key — NOT NULL
  • name (user_name) — VARCHAR(50) — NOT NULL
  • email (user_email) — VARCHAR(100) — NOT NULL
  • password (user_password) — VARCHAR(100) — NOT NULL
  • registered_day (user_registered_day) — DATETYPE
  • nickname (user_nickname) — VARCHAR(50)