Shulou(Shulou.com)06/02 Report--

This article mainly explains "what to do wrong in using koa-mysql-session Times". Friends who are interested might as well take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn "what to do when using the koa-mysql-session Times wrong".

Description

There is no problem testing the code locally, but an error is reported when deployed to the server.

Error

> cross-env WEBPACK_TARGET=node NODE_ENV=production node. / server/app.jstruethe server is start at port 3333/usr/share/nginx/nav/server/node_modules/koa-mysql-session/node_modules/co/index.js:292 throw err; ^ Error: ER_INDEX_COLUMN_TOO_LONG: Index column size too large. The maximum column size is 767 bytes.

Reason: due to different versions of mysql, 5.7locally, 5.6on the server. Koa-mysql-session is a 4-year-old package that is not recommended.

Limit on the length of a single-column index: no more than 767 bytes by default, no more than 3072bytes.

Resolve:

Create mysql_session_store manually

CREATE TABLE `_ mysql_session_ store` (`id` varchar (255) NOT NULL

`roomres` bigint (20) DEFAULT NULL

`data`text

PRIMARY KEY (`id`)

(ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC; here, I believe you have a deeper understanding of "what to do wrong with the koa-mysql-session Times". You might as well do it in practice! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.