-
Notifications
You must be signed in to change notification settings - Fork 0
/
cnit8.sql
307 lines (280 loc) · 35.8 KB
/
cnit8.sql
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
/*
Navicat Premium Data Transfer
Source Server : localhost_3306
Source Server Type : MariaDB
Source Server Version : 100213
Source Host : localhost:3306
Source Schema : cnit8
Target Server Type : MariaDB
Target Server Version : 100213
File Encoding : 65001
Date: 29/06/2018 18:15:36
*/
SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS = 0;
-- ----------------------------
-- Table structure for cn_admin
-- ----------------------------
DROP TABLE IF EXISTS `cn_admin`;
CREATE TABLE `cn_admin` (
`id` int(8) NOT NULL AUTO_INCREMENT,
`user_name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`password` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`sex` tinyint(1) NOT NULL,
`phone` varchar(16) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`real_name` varchar(40) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`address` varchar(140) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`picture` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`auth_id` int(5) NOT NULL,
`safety_code` varchar(10) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`work_status` tinyint(1) NOT NULL,
`token` varchar(512) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`last_time` datetime(0) NOT NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE CURRENT_TIMESTAMP,
`last_ip` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`create_time` datetime(0) NOT NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE CURRENT_TIMESTAMP,
`update_time` datetime(0) NOT NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 7 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_admin
-- ----------------------------
INSERT INTO `cn_admin` VALUES (5, 'admin', '2d2a21b2754a45c815efa9d2e1be8459', 1, '18729309523', 'rongqiu', 'xian', 'sss', 1, '2048', 1, 'ssss', '2018-06-29 15:40:23', '127.0.0.1', '2018-06-29 15:40:23', '2018-06-29 15:40:23');
-- ----------------------------
-- Table structure for cn_advertisement
-- ----------------------------
DROP TABLE IF EXISTS `cn_advertisement`;
CREATE TABLE `cn_advertisement` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`type_id` smallint(6) NOT NULL,
`ad_url` varchar(1000) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`ad_description` varchar(240) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`ad_image` varchar(500) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`ad_image_alt` varchar(60) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`is_delete` tinyint(1) NOT NULL,
`author` varchar(40) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`create_time` datetime(0) NULL DEFAULT NULL,
`update_time` datetime(0) NULL DEFAULT NULL,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 12 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_advertisement
-- ----------------------------
INSERT INTO `cn_advertisement` VALUES (1, 2, 'http://tp5.com/admin/advertisement/advertisementEdit.html', '这是百度跳转', '/upload/advertisement/20180605/de2ea706b4fb976368fe1f81a5b84631.jpg', '八度图片', 0, 'admin', '2018-06-05 17:32:59', '2018-06-06 10:21:01');
INSERT INTO `cn_advertisement` VALUES (2, 2, 'http://tp5.com', '这是一个神奇的网站', '/upload/advertisement/20180606/74cd01e3cce9b269dd7ef88644a10be3.jpg', '神奇的网站', 0, 'admin', '2018-06-06 11:14:33', NULL);
INSERT INTO `cn_advertisement` VALUES (3, 2, 'http://tp5.com/', 'http://tp5.com/', '/upload/advertisement/20180606/d5982d16daad70bf06335e68a1bd1cc0.jpg', '描述测试', 0, 'admin', '2018-06-06 11:15:51', NULL);
INSERT INTO `cn_advertisement` VALUES (4, 1, 'http://tp5.com', '这是一个神奇的网站', '/upload/advertisement/20180606/035da2d56daa94beaa6193cddddb884e.jpg', '描述测试', 0, 'admin', '2018-06-06 11:42:40', NULL);
INSERT INTO `cn_advertisement` VALUES (5, 2, 'http://tp5.com', '这是一个神奇的网站', '/upload/advertisement/20180606/3c2eddcddf7e231354cf5151755632d6.jpg', '描述测试', 0, 'admin', '2018-06-06 11:46:18', '2018-06-06 11:48:46');
INSERT INTO `cn_advertisement` VALUES (6, 2, 'http://tp5.com', '这是一个神奇的网站是是是', '/upload/advertisement/20180606/8ac4d68d7b05274ba7474948f00048eb.jpg', '神奇的网站', 0, 'admin', '2018-06-06 11:46:54', NULL);
INSERT INTO `cn_advertisement` VALUES (7, 1, 'http://tp5.com', '这是一个神奇的网站是是是', '/upload/advertisement/20180606/173006b6868293523c042a54f2235c21.jpg', '神奇的网站', 0, 'admin', '2018-06-06 11:55:54', NULL);
INSERT INTO `cn_advertisement` VALUES (8, 4, 'http://tp5.com', '方法获取不到值的安全替换方法', '/upload/advertisement/20180606/56c4c8a76eb7394a5b5a3e07641345a5.jpg', '方法获取不到值的安全替换方法', 0, 'admin', '2018-06-06 17:20:43', NULL);
INSERT INTO `cn_advertisement` VALUES (9, 4, 'http://tp5.com', '测试方法获取不到值的安全替换方法', '/upload/advertisement/20180606/05148aa42ad47479e8ef314fe81be07e.jpg', '方法获取不到值的安全替换方法', 0, 'admin', '2018-06-06 17:21:11', NULL);
INSERT INTO `cn_advertisement` VALUES (10, 4, 'http://tp5.com', '谁卡了就撒考虑进来看见', '/upload/advertisement/20180606/66b6f4387e2c8db1144968c1cbabef5a.jpg', '方法获取不到值的安全替换方法', 0, 'admin', '2018-06-06 17:22:02', NULL);
INSERT INTO `cn_advertisement` VALUES (11, 1, 'http://tp5.com/admin/advertisement/advertisementEdit.html', 'http://tp5.com/admin/advertisement/advertisementEdit.html', '/upload/advertisement/20180627/a9ce415e5dd8941eada20134b09d5618.jpg', 'http://tp5.com/admin/advertisement/advertisementEdit.html', 0, 'admin', '2018-06-27 15:35:34', NULL);
-- ----------------------------
-- Table structure for cn_advertisement_type
-- ----------------------------
DROP TABLE IF EXISTS `cn_advertisement_type`;
CREATE TABLE `cn_advertisement_type` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`type_name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`author` varchar(60) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`is_delete` tinyint(1) NOT NULL,
`create_time` datetime(0) NULL DEFAULT NULL,
`update_time` datetime(0) NULL DEFAULT NULL,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 5 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_advertisement_type
-- ----------------------------
INSERT INTO `cn_advertisement_type` VALUES (1, 'smallBanner', 'admin', 0, '2018-06-05 15:36:26', '2018-06-06 11:30:17');
INSERT INTO `cn_advertisement_type` VALUES (2, 'banner', 'admin', 0, '2018-06-05 15:54:45', '2018-06-05 16:07:40');
INSERT INTO `cn_advertisement_type` VALUES (3, 'product', 'admin', 0, '2018-06-05 16:07:27', NULL);
INSERT INTO `cn_advertisement_type` VALUES (4, '特别推荐', 'admin', 0, '2018-06-06 17:10:07', NULL);
-- ----------------------------
-- Table structure for cn_article
-- ----------------------------
DROP TABLE IF EXISTS `cn_article`;
CREATE TABLE `cn_article` (
`id` int(10) NOT NULL AUTO_INCREMENT,
`type_id` smallint(6) NOT NULL,
`title` varchar(200) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`keywords` varchar(240) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`description` varchar(400) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`author` varchar(20) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`image` varchar(500) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`is_top` tinyint(1) NOT NULL,
`add_time` datetime(0) NULL DEFAULT NULL,
`container` text CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`is_delete` tinyint(1) NOT NULL DEFAULT 0,
`create_time` datetime(0) NULL DEFAULT '0000-00-00 00:00:00',
`update_time` datetime(0) NULL DEFAULT NULL,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 13 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_article
-- ----------------------------
INSERT INTO `cn_article` VALUES (11, 10, 'PHP is a popular general-purpose scripting language that is especially suited to web development.', 'The PHP development team announces the immediate availability of PHP 7.1.18. All PHP 7.1 users are encouraged to upgrade to this version.', 'The PHP development team announces the immediate availability of PHP 7.1.18. All PHP 7.1 users are encouraged to upgrade to this version.', 'admin', '/upload/images/20180605/33029b8a8a1873ea9727c7c13e641877.png', 1, '2018-06-05 11:11:15', '<p>The PHP development team announces the immediate availability of PHP\r\n 7.1.18.\r\n \r\n All PHP 7.1 users are encouraged to upgrade to this version.</p><p>For source downloads of PHP 7.1.18 please visit our <a href=\"http://www.php.net/downloads.php\">downloads page</a>,\r\n Windows source and binaries can be found on <a href=\"http://windows.php.net/download/\">windows.php.net/download/</a>.\r\n The list of changes is recorded in the <a href=\"http://www.php.net/ChangeLog-7.php#7.1.18\">ChangeLog</a>.</p><p><br/></p>', 0, '2018-06-05 11:11:15', '2018-06-11 14:54:58');
INSERT INTO `cn_article` VALUES (12, 11, 'The BLOB and TEXT Types', 'The BLOB and TEXT Types', 'The BLOB and TEXT Types', 'admin', '/upload/images/20180605/47ef19dc2fb08eeb248f0a89a6e74374.png', 0, '2018-06-05 11:43:28', '<p>A <code class=\"literal\">BLOB</code> is a binary large object that can hold\r\n a variable amount of data. The four <code class=\"literal\">BLOB</code>\r\n types are <code class=\"literal\">TINYBLOB</code>, <code class=\"literal\">BLOB</code>, <code class=\"literal\">MEDIUMBLOB</code>, and <code class=\"literal\">LONGBLOB</code>.\r\n These differ only in the maximum length of the values they can\r\n hold. The four <code class=\"literal\">TEXT</code> types are <code class=\"literal\">TINYTEXT</code>, <code class=\"literal\">TEXT</code>, <code class=\"literal\">MEDIUMTEXT</code>, and <code class=\"literal\">LONGTEXT</code>.\r\n These correspond to the four <code class=\"literal\">BLOB</code> types and\r\n have the same maximum lengths and storage requirements. See <a class=\"xref\" href=\"https://dev.mysql.com/doc/refman/8.0/en/storage-requirements.html\" title=\"11.8 Data Type Storage Requirements\">Section 11.8, “Data Type Storage Requirements”</a>.</p><p><code class=\"literal\">BLOB</code> values are treated as binary strings\r\n (byte strings). They have the <code class=\"literal\">binary</code>\r\n character set and collation, and comparison and sorting are\r\n based on the numeric values of the bytes in column values. <code class=\"literal\">TEXT</code> values are treated as nonbinary strings\r\n (character strings). They have a character set other than <code class=\"literal\">binary</code>, and values are sorted and compared\r\n based on the collation of the character set.</p><p>If strict SQL mode is not enabled and you assign a value to a <code class=\"literal\">BLOB</code> or <code class=\"literal\">TEXT</code> column that\r\n exceeds the column's maximum length, the value is truncated to\r\n fit and a warning is generated. For truncation of nonspace\r\n characters, you can cause an error to occur (rather than a\r\n warning) and suppress insertion of the value by using strict SQL\r\n mode. See <a class=\"xref\" href=\"https://dev.mysql.com/doc/refman/8.0/en/sql-mode.html\" title=\"5.1.10 Server SQL Modes\">Section 5.1.10, “Server SQL Modes”</a>.</p><p>Truncation of excess trailing spaces from values to be inserted\r\n into <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/blob.html\" title=\"11.4.3 The BLOB and TEXT Types\"><code class=\"literal\">TEXT</code></a> columns always\r\n generates a warning, regardless of the SQL mode.</p><p>For <code class=\"literal\">TEXT</code> and <code class=\"literal\">BLOB</code> columns,\r\n there is no padding on insert and no bytes are stripped on\r\n select.</p><p>If a <code class=\"literal\">TEXT</code> column is indexed, index entry\r\n comparisons are space-padded at the end. This means that, if the\r\n index requires unique values, duplicate-key errors will occur\r\n for values that differ only in the number of trailing spaces.\r\n For example, if a table contains <code class=\"literal\">'a'</code>, an\r\n attempt to store <code class=\"literal\">'a '</code> causes a\r\n duplicate-key error. This is not true for <code class=\"literal\">BLOB</code> columns.</p><p>In most respects, you can regard a <code class=\"literal\">BLOB</code>\r\n column as a <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/binary-varbinary.html\" title=\"11.4.2 The BINARY and VARBINARY Types\"><code class=\"literal\">VARBINARY</code></a> column that\r\n can be as large as you like. Similarly, you can regard a <code class=\"literal\">TEXT</code> column as a <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/char.html\" title=\"11.4.1 The CHAR and VARCHAR Types\"><code class=\"literal\">VARCHAR</code></a> column. <code class=\"literal\">BLOB</code> and <code class=\"literal\">TEXT</code> differ from <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/binary-varbinary.html\" title=\"11.4.2 The BINARY and VARBINARY Types\"><code class=\"literal\">VARBINARY</code></a> and <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/char.html\" title=\"11.4.1 The CHAR and VARCHAR Types\"><code class=\"literal\">VARCHAR</code></a> in the following ways:</p><ul class=\"itemizedlist list-paddingleft-2\" style=\"list-style-type: disc;\"><li><p>For indexes on <code class=\"literal\">BLOB</code> and <code class=\"literal\">TEXT</code> columns, you must specify an index\r\n prefix length. For <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/char.html\" title=\"11.4.1 The CHAR and VARCHAR Types\"><code class=\"literal\">CHAR</code></a> and <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/char.html\" title=\"11.4.1 The CHAR and VARCHAR Types\"><code class=\"literal\">VARCHAR</code></a>, a prefix length is\r\n optional. See <a class=\"xref\" href=\"https://dev.mysql.com/doc/refman/8.0/en/column-indexes.html\" title=\"8.3.5 Column Indexes\">Section 8.3.5, “Column Indexes”</a>.</p></li><li><p><a class=\"indexterm\"></a>\r\n\r\n <a class=\"indexterm\"></a>\r\n\r\n <a class=\"indexterm\"></a>\r\n\r\n <code class=\"literal\">BLOB</code> and <code class=\"literal\">TEXT</code> columns\r\n cannot have <code class=\"literal\">DEFAULT</code> values.</p></li></ul><p>If you use the <code class=\"literal\">BINARY</code> attribute with a <code class=\"literal\">TEXT</code> data type, the column is assigned the\r\n binary (<code class=\"literal\">_bin</code>) collation of the column\r\n character set.</p><p><code class=\"literal\">LONG</code> and <code class=\"literal\">LONG VARCHAR</code> map\r\n to the <code class=\"literal\">MEDIUMTEXT</code> data type. This is a\r\n compatibility feature.</p><p>MySQL Connector/ODBC defines <code class=\"literal\">BLOB</code> values as <code class=\"literal\">LONGVARBINARY</code> and <code class=\"literal\">TEXT</code>\r\n values as <code class=\"literal\">LONGVARCHAR</code>.</p><p>Because <code class=\"literal\">BLOB</code> and <code class=\"literal\">TEXT</code>\r\n values can be extremely long, you might encounter some\r\n constraints in using them:</p><ul class=\"itemizedlist list-paddingleft-2\" style=\"list-style-type: disc;\"><li><p>Only the first <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_max_sort_length\"><code class=\"literal\">max_sort_length</code></a> bytes of\r\n the column are used when sorting. The default value of <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_max_sort_length\"><code class=\"literal\">max_sort_length</code></a> is 1024.\r\n You can make more bytes significant in sorting or grouping\r\n by increasing the value of <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_max_sort_length\"><code class=\"literal\">max_sort_length</code></a> at server\r\n startup or runtime. Any client can change the value of its\r\n session <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_max_sort_length\"><code class=\"literal\">max_sort_length</code></a>\r\n variable:</p><pre class=\"programlisting line-numbers language-sql\">mysql> SET max_sort_length = 2000;mysql> SELECT id, comment FROM t -> ORDER BY comment;</pre></li><li><p>Instances of <code class=\"literal\">BLOB</code> or <code class=\"literal\">TEXT</code> columns in the result of a query\r\n that is processed using a temporary table causes the server\r\n to use a table on disk rather than in memory because the <code class=\"literal\">MEMORY</code> storage engine does not support\r\n those data types (see <a class=\"xref\" href=\"https://dev.mysql.com/doc/refman/8.0/en/internal-temporary-tables.html\" title=\"8.4.4 Internal Temporary Table Use in MySQL\">Section 8.4.4, “Internal Temporary Table Use in MySQL”</a>). Use of disk\r\n incurs a performance penalty, so include <code class=\"literal\">BLOB</code> or <code class=\"literal\">TEXT</code> columns\r\n in the query result only if they are really needed. For\r\n example, avoid using <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/select.html\" title=\"13.2.10 SELECT Syntax\"><code class=\"literal\">SELECT *</code></a>,\r\n which selects all columns.</p></li><li><p>The maximum size of a <code class=\"literal\">BLOB</code> or <code class=\"literal\">TEXT</code> object is determined by its type,\r\n but the largest value you actually can transmit between the\r\n client and server is determined by the amount of available\r\n memory and the size of the communications buffers. You can\r\n change the message buffer size by changing the value of the <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_max_allowed_packet\"><code class=\"literal\">max_allowed_packet</code></a>\r\n variable, but you must do so for both the server and your\r\n client program. For example, both <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/mysql.html\" title=\"4.5.1 mysql — The MySQL Command-Line Tool\"><span class=\"command\"><strong>mysql</strong></span></a>\r\n and <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html\" title=\"4.5.4 mysqldump — A Database Backup Program\"><span class=\"command\"><strong>mysqldump</strong></span></a> enable you to change the\r\n client-side <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_max_allowed_packet\"><code class=\"literal\">max_allowed_packet</code></a> value.\r\n See <a class=\"xref\" href=\"https://dev.mysql.com/doc/refman/8.0/en/server-configuration.html\" title=\"5.1.1 Configuring the Server\">Section 5.1.1, “Configuring the Server”</a>, <a class=\"xref\" href=\"https://dev.mysql.com/doc/refman/8.0/en/mysql.html\" title=\"4.5.1 mysql — The MySQL Command-Line Tool\">Section 4.5.1, “<span class=\"command\"><strong>mysql</strong></span> — The MySQL Command-Line Tool”</a>, and <a class=\"xref\" href=\"https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html\" title=\"4.5.4 mysqldump — A Database Backup Program\">Section 4.5.4, “<span class=\"command\"><strong>mysqldump</strong></span> — A Database Backup Program”</a>.\r\n You may also want to compare the packet sizes and the size\r\n of the data objects you are storing with the storage\r\n requirements, see <a class=\"xref\" href=\"https://dev.mysql.com/doc/refman/8.0/en/storage-requirements.html\" title=\"11.8 Data Type Storage Requirements\">Section 11.8, “Data Type Storage Requirements”</a></p></li></ul><p>Each <code class=\"literal\">BLOB</code> or <code class=\"literal\">TEXT</code> value is\r\n represented internally by a separately allocated object. This is\r\n in contrast to all other data types, for which storage is\r\n allocated once per column when the table is opened.</p><p>In some cases, it may be desirable to store binary data such as\r\n media files in <code class=\"literal\">BLOB</code> or <code class=\"literal\">TEXT</code> columns. You may find MySQL's string\r\n handling functions useful for working with such data. See <a class=\"xref\" href=\"https://dev.mysql.com/doc/refman/8.0/en/string-functions.html\" title=\"12.5 String Functions\">Section 12.5, “String Functions”</a>. For security and other\r\n reasons, it is usually preferable to do so using application\r\n code rather than giving application users the <a class=\"link\" href=\"https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_file\"><code class=\"literal\">FILE</code></a> privilege. You can discuss\r\n specifics for various languages and platforms in the MySQL\r\n Forums (<a class=\"ulink\" href=\"http://forums.mysql.com/\" target=\"_top\">http://forums.mysql.com/</a>).</p><p><br/></p>', 0, '2018-06-05 11:43:28', NULL);
-- ----------------------------
-- Table structure for cn_article_type
-- ----------------------------
DROP TABLE IF EXISTS `cn_article_type`;
CREATE TABLE `cn_article_type` (
`id` int(3) NOT NULL AUTO_INCREMENT,
`type_name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '',
`create_user` varchar(30) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '',
`is_delete` tinyint(1) NOT NULL DEFAULT 0,
`create_time` datetime(0) NULL DEFAULT NULL,
`update_time` datetime(0) NULL DEFAULT NULL,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 15 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_article_type
-- ----------------------------
INSERT INTO `cn_article_type` VALUES (10, 'php', 'admin', 0, '2018-05-28 16:27:58', NULL);
INSERT INTO `cn_article_type` VALUES (11, 'mysqli', 'admin', 0, '2018-05-28 16:30:13', '2018-05-28 18:00:45');
INSERT INTO `cn_article_type` VALUES (12, 'javascript', 'admin', 0, '2018-05-28 16:30:31', '2018-05-28 18:39:45');
INSERT INTO `cn_article_type` VALUES (13, 'java', 'admin', 0, '2018-05-28 17:59:23', NULL);
INSERT INTO `cn_article_type` VALUES (14, 'html', 'admin', 0, '2018-05-28 18:38:17', NULL);
-- ----------------------------
-- Table structure for cn_config
-- ----------------------------
DROP TABLE IF EXISTS `cn_config`;
CREATE TABLE `cn_config` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`site_id` tinyint(1) NOT NULL,
`title` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`keywords` varchar(500) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`description` varchar(500) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`icp` varchar(40) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`author` varchar(60) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`create_time` datetime(0) NULL DEFAULT NULL,
`update_time` datetime(0) NOT NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 2 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_config
-- ----------------------------
INSERT INTO `cn_config` VALUES (1, 0, 'cnit8', 'cnit8', '测试的', '陕ICP10110号', 'admin', '2018-06-04 15:21:05', '2018-06-04 17:03:56');
-- ----------------------------
-- Table structure for cn_frontend_menu
-- ----------------------------
DROP TABLE IF EXISTS `cn_frontend_menu`;
CREATE TABLE `cn_frontend_menu` (
`id` int(3) NOT NULL AUTO_INCREMENT,
`sort` tinyint(2) NULL DEFAULT NULL,
`url` varchar(200) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`name` varchar(120) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`parent_id` int(3) NOT NULL,
`author` varchar(60) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`is_delete` tinyint(1) NOT NULL,
`create_time` datetime(0) NULL DEFAULT NULL,
`update_time` datetime(0) NULL DEFAULT NULL,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 10 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_frontend_menu
-- ----------------------------
INSERT INTO `cn_frontend_menu` VALUES (1, 0, 'baidu.com', '首页', 0, 'admin', 0, NULL, NULL);
INSERT INTO `cn_frontend_menu` VALUES (2, 0, 'tp5.com', '后端教程', 0, 'min', 0, NULL, NULL);
INSERT INTO `cn_frontend_menu` VALUES (3, 0, 'tp5', 'php', 2, 'ss', 0, NULL, NULL);
INSERT INTO `cn_frontend_menu` VALUES (4, 0, 'tp5', 'mysql', 2, 'admin', 0, NULL, NULL);
INSERT INTO `cn_frontend_menu` VALUES (5, 0, 'sadasd', '前端教程', 0, 'admin', 0, '2018-06-11 16:17:08', NULL);
INSERT INTO `cn_frontend_menu` VALUES (6, 0, 'java', 'Java', 2, 'admin', 0, '2018-06-11 16:21:09', NULL);
INSERT INTO `cn_frontend_menu` VALUES (7, 0, 'javaEE', 'javaEE', 2, 'admin', 0, '2018-06-11 16:21:44', NULL);
INSERT INTO `cn_frontend_menu` VALUES (8, 0, 'http://tp5.com/admin/config/frontendEdit.html', 'css', 5, 'admin', 0, '2018-06-28 14:40:10', NULL);
INSERT INTO `cn_frontend_menu` VALUES (9, 0, 'http://tp5.com/', '关于我们', 0, 'admin', 0, '2018-06-28 14:41:50', NULL);
-- ----------------------------
-- Table structure for cn_gallery
-- ----------------------------
DROP TABLE IF EXISTS `cn_gallery`;
CREATE TABLE `cn_gallery` (
`id` int(6) NOT NULL AUTO_INCREMENT,
`type_id` smallint(6) NOT NULL,
`image_url` varchar(400) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '',
`alt` varchar(120) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '',
`is_delete` tinyint(1) NOT NULL,
`create_time` datetime(0) NULL DEFAULT NULL,
`update_time` datetime(0) NULL DEFAULT NULL,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 71 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_gallery
-- ----------------------------
INSERT INTO `cn_gallery` VALUES (59, 5, '/upload/gallery/20180605/db98721381082d7cfaa6038aea2f7851.jpg', '', 0, '2018-06-05 11:40:13', NULL);
INSERT INTO `cn_gallery` VALUES (60, 5, '/upload/gallery/20180605/7a7043220012f890b58d98d166b66d75.jpg', '', 0, '2018-06-05 11:40:13', NULL);
INSERT INTO `cn_gallery` VALUES (61, 5, '/upload/gallery/20180605/d3ef60c050eeb6536df1804835246ebb.jpg', '', 0, '2018-06-05 11:40:13', NULL);
INSERT INTO `cn_gallery` VALUES (62, 5, '/upload/gallery/20180605/a485fe8da6d1f13c21f26d863f2773d2.jpg', '', 0, '2018-06-05 11:40:13', NULL);
INSERT INTO `cn_gallery` VALUES (63, 5, '/upload/gallery/20180612/f32849b3e14cf5998bb71ad90029ef9f.jpg', '', 0, '2018-06-12 19:27:05', NULL);
INSERT INTO `cn_gallery` VALUES (64, 5, '/upload/gallery/20180612/2bf22183350f0ceb2b9311eb5a65ebf8.jpg', '', 0, '2018-06-12 19:27:05', NULL);
INSERT INTO `cn_gallery` VALUES (65, 5, '/upload/gallery/20180612/12163954f8d3ac82c4558a40ec4fce83.jpg', '', 0, '2018-06-12 19:27:05', NULL);
INSERT INTO `cn_gallery` VALUES (66, 5, '/upload/gallery/20180612/96963fe388c53bf5daa05ed6e7b3b831.jpg', '', 0, '2018-06-12 19:27:05', NULL);
INSERT INTO `cn_gallery` VALUES (67, 5, '/upload/gallery/20180612/50df1743d886ad26977e5c2883085f6a.jpg', '', 0, '2018-06-12 19:27:05', NULL);
INSERT INTO `cn_gallery` VALUES (68, 5, '/upload/gallery/20180612/5e3af1c174ef9ec90c0a618ada81cc01.jpg', '', 0, '2018-06-12 19:27:05', NULL);
INSERT INTO `cn_gallery` VALUES (69, 5, '/upload/gallery/20180612/537ecebd9e2cd2fd364f3e2cae9d1c6a.jpg', '', 0, '2018-06-12 19:27:05', NULL);
INSERT INTO `cn_gallery` VALUES (70, 5, '/upload/gallery/20180612/a5f7f3af862f1f2339aea00ca15dc05a.jpg', '', 0, '2018-06-12 19:27:05', NULL);
-- ----------------------------
-- Table structure for cn_gallery_type
-- ----------------------------
DROP TABLE IF EXISTS `cn_gallery_type`;
CREATE TABLE `cn_gallery_type` (
`id` tinyint(1) NOT NULL AUTO_INCREMENT,
`type_name` varchar(120) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`image_url` varchar(400) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
`alt` varchar(60) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
`create_user` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`is_delete` tinyint(1) NOT NULL,
`create_time` datetime(0) NULL DEFAULT NULL,
`update_time` datetime(0) NULL DEFAULT NULL,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 6 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_gallery_type
-- ----------------------------
INSERT INTO `cn_gallery_type` VALUES (1, '我的图库', '/upload/images/20180528/b132eedf0f7eb58593ee82e1fd8e97ce.jpg', '我的图片', 'admin', 0, '2018-05-30 18:09:39', NULL);
INSERT INTO `cn_gallery_type` VALUES (2, '旅行', NULL, NULL, 'admin', 0, '2018-05-30 18:29:01', NULL);
INSERT INTO `cn_gallery_type` VALUES (3, '测试1', NULL, NULL, 'admin', 0, '2018-05-30 18:49:29', '2018-05-30 18:49:50');
INSERT INTO `cn_gallery_type` VALUES (4, '日志', NULL, NULL, 'admin', 0, '2018-05-31 16:34:32', NULL);
INSERT INTO `cn_gallery_type` VALUES (5, 'cesss', NULL, NULL, 'admin', 0, '2018-06-01 18:49:41', NULL);
-- ----------------------------
-- Table structure for cn_site
-- ----------------------------
DROP TABLE IF EXISTS `cn_site`;
CREATE TABLE `cn_site` (
`id` tinyint(2) NOT NULL AUTO_INCREMENT,
`url` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`site_name` varchar(60) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`description` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
`author` varchar(40) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`create_time` datetime(0) NULL DEFAULT NULL,
`update_time` datetime(0) NOT NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 2 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of cn_site
-- ----------------------------
INSERT INTO `cn_site` VALUES (1, 'http://www.tp5.com', 'tp5', 'composer require', 'admin', '2018-06-04 16:52:04', '0000-00-00 00:00:00');
-- ----------------------------
-- Table structure for it_admin
-- ----------------------------
DROP TABLE IF EXISTS `it_admin`;
CREATE TABLE `it_admin` (
`id` int(10) NOT NULL AUTO_INCREMENT COMMENT 'di主键',
`loginName` varchar(36) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '登录名',
`passWord` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`realName` varchar(36) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '真实姓名',
`sex` tinyint(1) NOT NULL DEFAULT 1 COMMENT '性别',
`email` varchar(40) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '邮箱',
`phone` varchar(15) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '手机',
`workStatus` tinyint(1) NOT NULL DEFAULT 1 COMMENT '状态',
`lastIP` varchar(30) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`lastTime` datetime(0) NOT NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE CURRENT_TIMESTAMP,
`created_at` timestamp(0) NOT NULL DEFAULT current_timestamp() COMMENT '创建时时间',
`updated_at` timestamp(0) NOT NULL DEFAULT current_timestamp() COMMENT '升级时间',
PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 2 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
-- ----------------------------
-- Records of it_admin
-- ----------------------------
INSERT INTO `it_admin` VALUES (1, 'admin', 'eyJpdiI6InVmT3hcLytVMWlHRENxZlZuV1BLMkRBPT0iLCJ2YWx1ZSI6ImZhN1BIM3dKVGRheE1pRnZ5N3lpSlE9PSIsIm1hYyI6ImNkZmU5NmZmZGNmNjQzOGRiMDhjNjI3MTRkODhmOTkxYmY4ZjM0Njk4N2E5NTgyODU2ZjI2MGM1ODhmNDMxNDMifQ==', 'admin', 1, '375170667@qq.com', '', 1, '127.0.0.1', '2018-05-11 06:23:36', '2018-03-07 19:02:31', '0000-00-00 00:00:00');
SET FOREIGN_KEY_CHECKS = 1;