Bug #18962
closed
innodb-commands in sql-files crash adodb and dbal
0%
Description
hi!
adodb and dbal have problems with the innodb-addition to some create-table-commands.
every sql-command with "ENGINE=InnoDB;" makes adodb/dbal crash and showing me the following error:
ERROR: Query could not be parsed: "SQL engine parse ERROR: No action CHANGE, DROP or ADD found!: near "ENGINE=InnoDB "". Query: "ALTER TABLE cache_hash ENGINE=InnoDB;"
i'm wondering no other adodb-user has experiences this error.
btw, i'm using postgresql.
(issue imported from #M8718)
Updated by Mangan almost 16 years ago
Hello everybody,
Ingo, I'm completely with you! Have the same error here. And I did a completely fresh install of Typo3 on a completely fresh PostgreSQL DB.
Unfortunately I experienced A LOT of problems with PostgreSQL. This is just one still unsolved, but I sincerely hope that some really good core developer will care about making the core REALLY DBAL compatible. Please, let the PostgreSQL community grow and make the core compatible soon. Thank you a lot. If you need any professional testing I am with you.
Mangan
Updated by Anonymous almost 16 years ago
dbal and adodb is the completely wrong way. they should go with pdo in typo3 5.0
Updated by Mangan almost 16 years ago
As far is I see, PDO is not on the roadmap yet.
I keep on deleting every "ENGINE=..." in the ext_tables.sql files - works if there are no other problems ;-)
Updated by Matthias over 15 years ago
This error occured when i tried to install indexed search engine. I deactivated DBAL an installed the extension. Activated DBAL again. Works.
Updated by Chris topher almost 14 years ago
Is it still a problem in 4.4beta2 or newer?
Updated by Chris topher almost 14 years ago
According to Xavier in #19030 this has been fixed:
"This problem cannot be reproduced on TYPO3 4.3 beta3. Extension manager still proposes to ALTER TABLE with Engine=InnoDB as it does not exist on another plateform than MySQL but tables are created and usable anyway."