2012-01-23 - [GRASE-Hotspot] #47: Investigate UTF8 .vs. latin1 in MySQL
Header Data
From: GRASE Trac <tr***c@grasehotspot.org>
Message Hash: 3f03af2ea5dd1c03750438cca89316a05403525d123c0facf7ac176b50c6b216
Message ID: <039.e7ee49450031548d3fc2e8d0c2427eae@grasehotspot.org>
Reply To: N/A
UTC Datetime: 2012-01-23 17:17:43 UTC
Raw Date: Tue, 24 Jan 2012 00:17:43 -0000
Raw message
#47: Investigate UTF8 .vs. latin1 in MySQL
---------------------------+-----------------
Reporter: tim | Owner: tim
Type: enhancement | Status: new
Priority: major | Milestone: 4.0
Component: Other Backend | Version: 3.6
Keywords: utf8, mysql |
---------------------------+-----------------
Currently we store data in latin1 in MySQL. Given that we are an
international project, and that templates and such should be using utf8,
we need to look at converting everything to utf8, including the database
tables
--
Ticket URL: <http://trac.grasehotspot.org/ticket/47>
GRASE Hotspot <http://grasehotspot.org/>
GRASE Hotspot bug tracker
Thread
- Return to January 2012
-
Return to June 2013
-
Return to “GRASE Trac <tr***c@grasehotspot.org>”
- 2012-01-23 (Tue, 24 Jan 2012 00:17:43 -0000) - [GRASE-Hotspot] #47: Investigate UTF8 .vs. latin1 in MySQL - GRASE Trac <tr***c@grasehotspot.org>
- 2013-06-22 (Sat, 22 Jun 2013 13:58:08 -0000) - Re: [GRASE-Hotspot] #47: Investigate UTF8 .vs. latin1 in MySQL - GRASE Trac <tr***c@grasehotspot.org>