Bug #35843
closed
Incompatibilies in PostgreSQL integration due to use of MySQL-specific functions
0%
Description
In 4.5.3, TYPO3 introduced the usage of the MySQL "find_in_set" function. Since then, it also expects
any given DBMS to have this function, which e.g. PostgreSQL does not have. This leads to having to use
workarounds in the form of the supplied file /typo3/sysext/dbal/res/postgresql/postgresql-compatibility.sql.
Unfortunately, the execution of this file requires the PostgreSQL database to incorporate the plpgsql extension,
which the user is never told to install and won't be installed by the TYPO3 installer. The missing
"find_in_set" function also causes the TYPO3 framework to not find pages created in the backend,
which renders it unusable.
These are some possible solutions we came up with:
- revise the usage of "find_in_set" and maybe resort to proprietary functions
- resort to proprietary PostgreSQL functions when a PgSQL DBMS is selected
- require the user to have plpgsql installed in order to select a PgSQL DBMS
- implement the creation of the compatibility layer without using plpgsql
Tested versions: 4.6.4 and 4.7.0b3
Updated by Michael Stucki about 11 years ago
- Project changed from 329 to TYPO3 Core
Updated by Mathias Schreiber almost 10 years ago
- Status changed from New to Resolved
- TYPO3 Version set to 4.5
- Is Regression set to No
Solution 5:
Install the provided Stored Procedure from DBAL.
:)
Updated by Mathias Schreiber almost 10 years ago
- Status changed from Resolved to New
- Target version set to 7.5
scratch the last remark... too late for me...
Updated by Mathias Schreiber almost 10 years ago
- Status changed from New to Closed
still.. we'll continue in #29024