Project

General

Profile

Actions
Copy link

Bug #16594

closed

Installer cannot import tables when the db has a collation of utf8_unicode_ci

Added by Daniel Mueller about 18 years ago. Updated about 6 years ago.

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

0%

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

Description

The db dumps in the dummy package have a collation of latin1_swedish_ci.
If the installer creates the db, everything goes alright, because the installer creates
a db with this collation. however if you want to use a different collation e.g.
utf8_unicode_ci and create the db yourself, the import of the dumps failes naturally.

(issue imported from #M4281)

Related issues 3 (0 open — 3 closed)

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 #16388: Installer should honour forceCharset setting when creating a DBClosedChris topher2006-07-21

Actions
Actions
Copy link
 #1

Updated by Chris topher over 14 years ago

I just checked that with current trunk (4.4.beta2):
I cannot reproduce this problem.

I can import tables into the DB no matter if I choose latin1_swedish_ci or utf8_unicode_ci as DB collation when I create the DB in phpmyadmin before.

I even checked this with an old dump, which comes with the Testsite package of TYPO3 3.8.1: I had to do some updates using "Compare", but afterwards it worked.

Actions
Copy link
 #2

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF