我正在从旧表重新创建数据库结构。新表应该优化并易于理解。
在旧数据库中,开发人员使用video表名来存储视频博客。然而,我不认为这是一个适当的名称存储视频博客。下面是旧桌子
video:
_attributes: { phpName: Video }
ID: { type: INTEGER, size: '11', primaryKey: true, autoIncrement: true, required: true }
coupon_banner_id: { type: INTEGER, size: '10', foreignTable: coupon_banner, foreignReference: id, onUpdate: CASCADE, onDelete: CASCADE }
blog: { type: TINYINT, size: '1', required: true, defaultValue: '0' }
catid: { type: INTEGER, size: '11', required: true, defaultValue: '0' }
title: { type: VARCHAR, size: '100', required: true, defaultValue: '' }
description: { type: LONGVARCHAR, required: true }
blogtopid: { type: INTEGER, size: '11', required: true, defaultValue: '1' }
video: { type: VARCHAR, size: '50', required: true, defaultValue: '' }
vlink: { type: LONGVARCHAR, required: true }
picture: { type: VARCHAR, size: '255', required: true, defaultValue: '' }
video_picture_alt: { type: VARCHAR, size: '255', required: false, defaultValue: '' }
apicture: { type: VARCHAR, size: '150', required: true, defaultValue: '' }
usid: { type: INTEGER, size: '11', required: true, defaultValue: '0' }
datein: { type: TIMESTAMP, required: true, defaultValue: '0000-00-00 00:00:00' }
koview: { type: INTEGER, size: '11', required: true, defaultValue: '0' }
korating: { type: INTEGER, size: '11', required: true, defaultValue: '0' }
kototrat: { type: INTEGER, size: '11', required: true, defaultValue: '0' }
konota: { type: INTEGER, size: '11', required: true, defaultValue: '0' }
kocomm: { type: INTEGER, size: '11', required: true, defaultValue: '0' }
kofavorite: { type: INTEGER, size: '11', required: true, defaultValue: '0' }
kofeatured: { type: INTEGER, size: '11', required: true, defaultValue: '0' }
koorder: { type: INTEGER, size: '11', required: true, defaultValue: '999' }
commtime: { type: TIMESTAMP, required: true, defaultValue: '0000-00-00 00:00:00' }
is_active: { type: BOOLEAN, required: true, defaultValue: '0'}
slug: { type: VARCHAR, size: '100', required: true, defaultValue: '' }
video_cat:
_attributes: { phpName: VideoCat }
ID: { type: INTEGER, size: '11', primaryKey: true, autoIncrement: true, required: true }
category: { type: VARCHAR, size: '50', required: true, defaultValue: '' }
meta_title: { type: VARCHAR, size: '255', required: true, defaultValue: '' }
category_desc: { type: LONGVARCHAR, required: false, defaultValue: '' }
meta_desc: { type: LONGVARCHAR, required: false, defaultValue: '' }
position: { type: INTEGER, size: '3', required: true, defaultValue: '999' }我重新命名了它,并对它进行了如下优化:
article:
id,
category_id,
user_id,
title,
slug,
description,
video_link,
video_description,
video_thumbnail,
Video_thumbnail_alt,
article_description ( I will be using CKEditor here so styles, which data type is better text or longvarchar? ),
is_active (int or boolean which one is better),
is_featured (int or boolean which one is better),
is_favorite (int or boolean which one is better),
created_at DATETIME,
updated_at DATETIME你认为在我的新优化表中还需要改进什么?我还想知道,在一个单独的表中存储视频和文章更好,还是可以像我正在做的那样存储在同一张表中?
发布于 2018-12-06 22:27:22
分开或不分开的桌子--这取决于
如果一个视频可以在多个类别中,你将需要一个多到多映射表.
什么是position,它将如何维护?
https://dba.stackexchange.com/questions/224312
复制相似问题