Bug #14476
closed
SQL parser in Extension Manager has trouble with various data types
0%
Description
When trying to install extensions in 3.7.0, several SQL statements cause trouble. The BIGINT one reported in http://bugs.typo3.org/bug_view_page.php?bug_id=0000546, but also unknown data type SET with the Visitor Tracking System (de_phpot).
Trying to find a place where data types are checked, until now I only found line 933 in t3lib/class.t3lib_sqlparser.php. Bigint isn't in there, Set and Enum neither.
After adding |bigint|set|enum to the end of the field type list, it did work. Hope this is the right place :-)
(issue imported from #M651)
Updated by Karsten Dambekalns over 19 years ago
The type BIGINT is supported in CVS.
I would not like to add SET and ENUM, as those are MySQL-specific types with no corresponding type in most other databases nor in standard SQL. Since the whole point of adding the sql parser to TYPO3 was to enable the possibility for DBAL, this would be counter-productive.
Updated by Michael Stucki over 19 years ago
Please ask the guy who wrote the vts extension to change the data type since it's not allowed by DBAL (right, Karsten?)
Updated by Karsten Dambekalns over 19 years ago
Today I checked, and could flawlessly install the Visitor Tracking extension, although it uses ENUM and SET. So this seems to be an issue any longer, as long DBAL is not used.
@Stuckii: Changing the tables might not be too easy, as the VTS is just a "wrapper" around phpOpenTracker, IIRC. But in theory this is right, it's not DBAL-compliant and thus should be changed.
Updated by Michael Stucki over 19 years ago
Fine, so then let's close this one. Thanks for your feedback, Karsten!