Bug #82465
closed
Schema column definition handling with Doctrine fails for Oracle DB (OCI8)
0%
Description
When running the install tool database analyzer or running the report module that both need to fetch the column definitions from registered databases, an error occurs if an Oracle database is registered.
This is due to the type of a column that is set in the data_type key of the definition array (only for Oracle), when TYPO3 works with the type key.
See Oracle official documentation for more information.
We run into this issue on a 8.7.4 version, with a second Oracle database registered (the default DB runs on MySQL just fine). Frontend database requests with the Oracle database work fine.
Updated by
Updated by Christian Kuhn about 7 years ago
- Status changed from New to Rejected
Hey moin :)
Oracle is currently not supported at all (and will not be for v8 at least). At the moment nobody in the core really picked up oracle, we're supporting postgres, mssql, mysql and the next thing would probably be sqlite.
This topic will only be solved if anyone seriously picks up issues, starts bug fixing, starts creating (extending) current test setup (eg. bamboo) and finds at least one core team member who actively reviews and pushes the topic and steers this project.
Until this happens, casual issues related to oracle like this "wrong type" one will be closed as 'rejected'.
If you have a strong urge to have a working oracle support in the core, feel free to contact me and we could chat a bit about details on what would be needed to achieve that in an sustainable way.
Updated by Gerrit Code Review about 7 years ago
- Status changed from Rejected to Under Review
Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54130
Updated by Tymoteusz Motylewski about 7 years ago
- Status changed from Under Review to Rejected