[TYPO3-core] FYI #14456: SQL parser doesn't accept ALTER TABLE statement without CHANGE, DROP or ADD keyword

Xavier Perseguers typo3 at perseguers.ch
Thu May 27 17:49:11 CEST 2010


Hi,

FYI, I committed enclosed patches to:

- TYPO3 trunk (rev. 7697)
- DBAL trunk (rev. 33591)
- DBAL_1-1 (rev. 33592)


Type: Bugfix

Bugtracker reference:
http://bugs.typo3.org/view.php?id=14456

Branches: Core trunk, DBAL trunk, DBAL_1-1

Problem reported by Francois Suter:
When using the introductionpackage with PostgreSQL, the process fails with error

SQL parser doesn't accept ALTER TABLE statement without CHANGE, DROP or ADD keyword

This means the SQL parser won't accept a statement like:

ALTER TABLE tx_realurl_pathcache ENGINE=InnoDB;

Solution:
Enhance the SQL parser

Note #1:
Successfully reproduced and tested with Oracle in addition to the unit tests

Note #2:
I know have to face another limitation of parser in 1-2-3 with introductionpackage:

ERROR: Query could not be parsed: "SQL engine parse ERROR: No table found!: near "`index_phash` DEFAULT CHARACTER SET utf8 "". Query: "ALTER TABLE `index_phash` DEFAULT CHARACTER SET utf8"

-- 
Xavier Perseguers
http://xavier.perseguers.ch/en
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 14456_core.diff
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100527/bb65cf32/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 14456_dbal.diff
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100527/bb65cf32/attachment.asc>


More information about the TYPO3-team-core mailing list