Project

General

Profile

Actions

Bug #29024

closed

postgresql and typo3 v4.5.3 crash

Added by Jigal van Hemert over 13 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
Start date:
2011-06-28
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

After installation of 4.5.3 the following error occurs:
Page not found!
The requested page does not exist.
While exactly the same set-up (default template and one root page) works with 4.4.8
Also errors when upgrading from 4.4.8 to 4.5.3 gives this error and when you compare the database TYPO3 wants to truncate all the tables (be_group, be_users etc.).
A major error. There is no error warning what so ever. I did this on a windows machine, 2 Linux servers, and always the same error.
I used the latest 4.5.3 blank package (tar) and also i tested the blank package (zip) and the introduction package. All was tested with php5.3. and postgresql 8.4.1.
When I use Typo3 4.4.8 there al no problems.

Moved from: http://bugs.typo3.org/view.php?id=18198


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #35843: Incompatibilies in PostgreSQL integration due to use of MySQL-specific functionsClosed2012-04-11

Actions
Actions #1

Updated by Jigal van Hemert about 13 years ago

It turned out that /typo3/sysext/dbal/res/postgresql/postgresql-compatibility.sql was not executed. This script also requires plpgsql to be installed.
Check for plpgsql [1] :
SELECT COUNT FROM pg_language WHERE lanname = 'plpgsql'

Possible solution:
In the 1-2-3 installer:
- create routine for checking presence of plpgsql (can be extra step in tx_dbal_installtool::excuteStepOutput()?)
- execute the postgresql-compatibility.sql (can be done with pg_send_query())
In the upgrade module of the Install Tool:
- check for Posgresql used in dbal, then do the same two steps as above.

[1] http://www.polak.ro/postgres-how-to-check-if-plpgsql-is-installed.html

Actions #2

Updated by Gerrit Code Review almost 12 years ago

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/16703

Actions #3

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/21087

Actions #4

Updated by Michael Stucki almost 11 years ago

  • Category deleted (PostgreSQL)
Actions #5

Updated by Michael Stucki almost 11 years ago

  • Project changed from 329 to TYPO3 Core
Actions #6

Updated by Michael Stucki almost 11 years ago

  • Category set to 999
Actions #7

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.5
  • TYPO3 Version set to 4.5
  • Is Regression set to No
Actions #8

Updated by Gerrit Code Review over 9 years ago

  • Status changed from New to Under Review

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/21087

Actions #9

Updated by Benni Mack over 9 years ago

  • Status changed from Under Review to Needs Feedback

Hey Jigal,

do you still have that problem? I abandoned the solution in Gerrit as there was no progress and the code was completely outdated for 6.2 and master. If you still need this, could you please create a new patch for this? Otherwise, you can close this issue.

Actions #10

Updated by Jigal van Hemert over 9 years ago

  • Status changed from Needs Feedback to Closed

Judging from the text that was migrated from Mantis, I think I filed the issue for someone else. Code has changed so much in the mean time. Closed.

Actions

Also available in: Atom PDF