From 8bba897a46e773c0155419abc7b0d9a1fb5fd7aa Mon Sep 17 00:00:00 2001 From: Andy Staudacher Date: Mon, 23 Feb 2009 06:33:10 +0000 Subject: Changing from binary(16) to char(32) as translation message key. Although less efficient as a storage / transmission / comparison format, it's friendlier on the eyes and universally supported. --- installer/install.sql | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'installer/install.sql') diff --git a/installer/install.sql b/installer/install.sql index 153057f1..349f0354 100644 --- a/installer/install.sql +++ b/installer/install.sql @@ -99,7 +99,7 @@ SET @saved_cs_client = @@character_set_client; SET character_set_client = utf8; CREATE TABLE `incoming_translations` ( `id` int(9) NOT NULL auto_increment, - `key` binary(16) NOT NULL, + `key` char(32) NOT NULL, `locale` char(10) NOT NULL, `message` text NOT NULL, `translation` text, @@ -201,7 +201,7 @@ SET @saved_cs_client = @@character_set_client; SET character_set_client = utf8; CREATE TABLE `outgoing_translations` ( `id` int(9) NOT NULL auto_increment, - `key` binary(16) NOT NULL, + `key` char(32) NOT NULL, `locale` char(10) NOT NULL, `message` text NOT NULL, `translation` text, -- cgit v1.2.3