From b3e18a850e09afc9f8b3e26c9af80e091ca66ccb Mon Sep 17 00:00:00 2001 From: Alexandre Alapetite Date: Tue, 19 Nov 2013 22:41:00 +0100 Subject: SQL : Explications sur le choix de varchar(760) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit varchar(760) est choisi pour pouvoir ĂȘtre utilisĂ© efficacement dans un UNIQUE() avec les limites de InnoDB de MySQL --- public/install.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'public') diff --git a/public/install.php b/public/install.php index 4471f2e95..ed7c5e3bb 100644 --- a/public/install.php +++ b/public/install.php @@ -43,7 +43,7 @@ define ('SQL_REQ_FEED', 'CREATE TABLE IF NOT EXISTS `%sfeed` ( define ('SQL_REQ_ENTRY', 'CREATE TABLE IF NOT EXISTS `%sentry` ( `id` char(6) NOT NULL, - `guid` varchar(760) CHARACTER SET latin1 NOT NULL, + `guid` varchar(760) CHARACTER SET latin1 NOT NULL, -- Maximum for UNIQUE is 767B `title` varchar(255) NOT NULL, `author` varchar(255) NOT NULL, `content` text NOT NULL, -- cgit v1.2.3