[TYPO3-core] FY #16501: DBAL does not support multi-column indexes in create table queries
Xavier Perseguers
typo3 at perseguers.ch
Tue Nov 30 16:29:16 CET 2010
Hi,
FYI, following patches were committed to:
- DBAL trunk (rev. 40682)
- Core trunk (rev. 9689)
- Core 4-4 (rev. 9690)
- Core 4-3 (rev. 9691)
Sidenote: I found one downside of the t3lib "cleanup": svn merge now
leads to conflicts when backporting changesets from trunk to older
branches. I know, I know... I'm for sure the only one working with svn
merge anyway ;-)
Type: Bug
Bugtracker reference:
http://bugs.typo3.org/view.php?id=16501
Branches: trunk, 4-4, 4-3 (for older I do not support DBAL anyway)
Problem:
When DBAL is active, the install tool tries to create the sys_registry
table. This table contains a UNIQUE key on two columns. The query parser
fails to recognize this and creates:
CREATE TABLE sys_registry ( uid int(11) unsigned NOT NULL
auto_increment, entry_namespace varchar(128) NOT NULL default '',
entry_key varchar(128) NOT NULL default '', entry_value blob, PRIMARY
KEY (uid), UNIQUE (Array) );
Analyze:
It happens when using DBAL with a MySQL DBMS.
Actually the problem is not in DBAL itself but in the Core SQL parser
which gets activated only when DBAL is loaded. Parsing of the create
table was OK but its "compilation" to get the SQL back wasn't.
Solution:
Fix it!
Thanks to Jigal van Hemert for the bug report.
Cheers
Xavier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 16501_core.diff
Type: text/x-diff
Size: 860 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101130/506a4252/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 16501_dbal.diff
Type: text/x-diff
Size: 1152 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101130/506a4252/attachment-0001.diff>
More information about the TYPO3-team-core
mailing list