Bug #83832
closedConstructing Tables With UTF-8 Special Characters
0%
Description
Environment
----------------------------------------
OS: Windows 8.1
PHP: 7.1.1
MySQL: 5.6.35
Typo3: 9.0
Server: Apache 2.4
Am unable to create table containing special characters in table names and field names using ext_tables.sql
Example
----------------------------------------
CREATE TABLE tx_orange__Ȼ0000000000 (
uid INT(11) unsigned NOT NULL auto_increment,
Ç0000000_00 TINYTEXT NOT NULL,
Ç0000000_01 BLOB,
Ç0000000_02 TEXT,
PRIMARY KEY (uid)
) ENGINE=MyISAM;
Additionaly, same problem occurs with ext_tables_static+tt.sql
Error upon execution
----------------------------------------
#1476340371: [SQL Error] line 0, col 20: Error: Expected TYPO3\CMS\Core\Database\Schema\Parser\Lexer::T_OPEN_PARENTHESIS, got 'Ȼ' in statement: CREATE TABLE tx_orange__Ȼ0000000000 ( uid INT unsigned NOT NULL auto_increment, Ç0000000_00 TINYTEXT NOT NULL, Ç0000000_01 BLOB, Ç0000000_02 TEXT, PRIMARY KEY (uid) ) ENGINE=MyISAM AUTO_INCREMENT=16; (More information)
Unsuccessful attempts
----------------------------------------
I've set charset to UTF8 in LocalConfiguration under DB->Connection->Default.
I have tried quoting the table names and fields and works but the problem persists when retrieving data from the database. Also persists when executing ext_tables_static+tt.sql setup as INSERT INTO tx_orange__Ȼ0000000000 VALUES with o without quotes.
Problem
----------------------------------------
What can I do to cause TYPO3 to work with special characters accepted by MySQL?
Updated by John Miller almost 7 years ago
- Project changed from 9 to TYPO3 Core
- Category set to Database API (Doctrine DBAL)
- Target version set to 9 LTS
- TYPO3 Version set to 9
- PHP Version set to 7.1
Updated by Christian Kuhn almost 7 years ago
- Status changed from New to Rejected
Hey John.
Thanks for your issue report. For the time being, we'd like to ask you to stick to [0-9,a-c,_] for table and column names. While your report is probably correct (didn't verify myself), it is unlikely we will fix that anytime soon.
I hope it's ok if I for now close the issue as "valid, won't fix".
Updated by John Miller almost 7 years ago
- Related to Feature #83846: Ability to determine own DB naming conventions. added