Bug #47984
closedBlank Install of TYPO3 v.6.1 not woking with PostgreSQL
0%
Description
i'm having problems with using typo3 v.6.1 with postgres.
an upgrade from an existing and working v.6.0.4 does not work anymore.
even a blank install of typo3 v.6.1 does not seem to work. here are the steps i performed:
1. unpacked typo3_src-6.1.0 and dummy-6.1.0
2. created typo3-database
3. typo3_src-6.1.0/typo3/sysext/dbal/res/postgresql/postgresql-compatibility.sql
3. started typo3 installer wizard, choosing postgres as database and inserting credentials
4. the wizard successfully connects to database, inserts tables and finishes
5. then trying to access the backend results in the following error:
Call to a member function qstr() on a non-object in .../typo3_src-6.1.0/typo3/sysext/dbal/Classes/Database/DatabaseConnection.php on line 1875
Updated by Thorsten Kahler over 11 years ago
- Assignee set to Xavier Perseguers
Can you check this, Xavier?
Updated by Xavier Perseguers over 11 years ago
Yes, will have a look. I suspect quite a few broken links since the move to mysqli
Updated by Xavier Perseguers over 11 years ago
- Status changed from New to Accepted
Updated by Gerald Buttinger over 11 years ago
thanks for looking into this!
i have a question however: postgres is listed as a supported database in TYPO3's system requirements. but at the moment there are some critical problems (e.g. install tool, extension manager, EXTBASE, etc.) effectively making TYPO3 more or less unusable with postgres atm. what i'd like to know is the type of commitment of the TYPO3 core-devs regarding postgres-support, -QA, -testing, etc. and also the future plans of the TYPO3-team regarding postgres-support. because if postgres is listed as a supported DB, i would expect a stable version of TYPO3 to be tested with postgres before release and thus work out-of-the-box, otherwise maybe that support should be listed as EXPERIMENTAL. i'm also asking this, because i'm evaluating the usage of postgres in a production environment. how would you evaluate this as a TYPO3-insider?
Updated by Xavier Perseguers over 11 years ago
To be honest the commitment and tests regarding other databases than MySQL is extremly low.
Extbase is preparing queries without the TYPO3 abstraction layer making extremely complicated (and double work) to then parse again the query to try to make it DBAL compliant. As such I personally don't consider Extbase shipped with Core as DBAL-compliant. As more and more modules and extensions (in core) are written in Extbase...
So at the moment each new version of TYPO3 is having less support for other DBMS. We would like to invert the tendancy but we will need force coming from DBAL users who are unfortunately not very present in the mailing lists and in gerrit reviews.
Updated by Gerrit Code Review over 11 years ago
Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20582
Updated by Xavier Perseguers over 11 years ago
- Status changed from Accepted to Under Review
Updated by Gerrit Code Review over 11 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20582
Updated by Gerrit Code Review over 11 years ago
Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/21086
Updated by Michael Stucki almost 11 years ago
- Project changed from 329 to TYPO3 Core
Updated by Mathias Schreiber almost 10 years ago
- Status changed from Under Review to Closed
- Is Regression set to No
closed due to request by Andreas Fernandez