Project

General

Profile

Actions
Copy link

Bug #16388

closed

Installer should honour forceCharset setting when creating a DB

Added by Martin Kutschker almost 18 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Chris topher
Category:
Install Tool
Target version:
-
Start date:
2006-07-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.0
PHP Version:
4
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Mysql supports a default charset and collation for a DB. The installer should use forceCharset.

Of course the 1-2-3 mode needs an additional charset field for supporting this feature.

(issue imported from #M3900)

Related issues 5 (0 open — 5 closed)

Related to TYPO3 Core - Bug #16387: DBAL should honour forceCharset settingClosedKarsten Dambekalns2006-07-21

Actions
Related to TYPO3 Core - Feature #17503: BE should check Mysql charset settingsClosedMichael Stucki2007-08-07

Actions
Related to TYPO3 Core - Feature #18501: Enable UTF-8 by defaultClosedMichael Stucki2008-03-26

Actions
Related to TYPO3 Core - Bug #16594: Installer cannot import tables when the db has a collation of utf8_unicode_ciClosedChris topher2006-09-26

Actions
Is duplicate of TYPO3 Core - Bug #22933: Install tool should by default create database with utf8 charsetClosedMichael Stucki2010-06-18

Actions
Actions
Copy link
 #1

Updated by Dmitry Dulepov almost 18 years ago

Disagree. Database charset may be different from BE charset. This is normal and was so.

Database charset is controlled by initialization strings in install tool. Use them. They are specially designed for this.

Actions
Copy link
 #2

Updated by Martin Kutschker almost 18 years ago

Think about it. If you use forceCharset then you should set the db to utf-8.

Actions
Copy link
 #3

Updated by Chris topher almost 14 years ago

Resolved as duplicate of #22933.

Actions
Copy link
 #4

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF