Bug #65026
closed
INSERT of ext_tables_static+adt.sql not mapped
0%
Description
Due to the wrong used database object the table names in an INSERT statement run in Install Tool are not mapped properly.
Updated by Gerrit Code Review almost 10 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/36859
Updated by Gerrit Code Review almost 10 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/36859
Updated by Gerrit Code Review almost 10 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/36859
Updated by Gerrit Code Review almost 10 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/36859
Updated by Mathias Schreiber about 9 years ago
- Target version deleted (
next-patchlevel)
Updated by Andreas Kienast almost 9 years ago
- Status changed from Under Review to New
- Target version set to 8 LTS
will be tackled with v8
Updated by Nicole Cordes almost 8 years ago
Which steps have to be done to reproduce the problem described?
Updated by Andreas Kienast almost 8 years ago
Puh, that's pretty old ;) IIRC the original table name and field names were used instead of the ones defined in the DBAL mapping. Means, you need to map a table to another name and in the Install Tool, the original name is still used.
Updated by Nicole Cordes almost 8 years ago
For better understanding the problem, see https://docs.typo3.org/typo3cms/extensions/dbal/Configuration/Mapping/Index.html with mapping examples. The problem seems to be that the file content of ext_tables_static+adt.sql files is either not parsed (and mapped) or something is broken inside the parser.
Updated by Benni Mack over 7 years ago
- Target version changed from 8 LTS to next-patchlevel
Updated by Christian Kuhn about 6 years ago
- Status changed from New to Closed
Hey. I'll take the freedom to close this: i'd guess that issue vanished in v8 - no dbal there, anymore. If still an issue and still needs a fix, it would probably go to the outsourced dbal ext anyway.