Bug #26687

UTF-8 support is broken

Added by Martin Brüggemann about 2 years ago. Updated about 2 years ago.

Status:Resolved Start date:2011-05-06
Priority:Must have Due date:
Assignee:Karsten Dambekalns % Done:

100%
Category:Persistence
Target version:TYPO3 Flow Base Distribution - 1.0 beta 1
PHP Version: Complexity:
Has patch: FLOW3 version affected:
Votes: 0

Description

I just saved some FLOW3 objects with german umlauts and it seems that there's a "SET NAMES UTF-8" or some Doctrine2 UTF-8 connection setting missing. Also all autogenerated MySQL tables have latin1_swedish_ci collation. Should be easy to fix this.

These are my connection settings in Settings.yaml

FLOW3:
  persistence:
    backendOptions:
      driver: pdo_mysql
      host: 127.0.0.1
      port: 3306
      dbname: guruhelp_local
      user: root
      password: dasistnureinhohlespasswortdaskeinerkennt
      path: guruhelp

wrong_utf8_encoded_object.png (57.8 kB) Martin Brüggemann, 2011-05-06 22:32

Associated revisions

Revision a1c06043
Added by Karsten Dambekalns about 2 years ago

[FEATURE] Enable SQL connection initialization

Some database setups might need to run some initial SQL statement after
a connection has been established. Examples are date/time format options
for Oracle or charset settings for MySQL.

For MySQL UTF-8 support was potentially broken, depending on the system
setup. This can be fixed by using the new initialization option:
FLOW3: persistence: doctrine: dbal:
sessionInitialization: 'SET NAMES utf8 COLLATE utf8_unicode_ci'

Change-Id: I456f313014e1943733aa5d7aa9cf9c8cb20f34a8
Fixes: #26687

History

#1
Updated by Karsten Dambekalns about 2 years ago

  • Category set to Persistence
  • Status changed from New to Accepted
  • Target version set to 1.0 beta 1

#2
Updated by Mr. Hudson about 2 years ago

Patch set 1 of change I456f313014e1943733aa5d7aa9cf9c8cb20f34a8 has been pushed to the review server.
It is available at http://review.typo3.org/2037

#3
Updated by Karsten Dambekalns about 2 years ago

  • Status changed from Accepted to Under Review

#4
Updated by Karsten Dambekalns about 2 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF