Actions
Bug #41362
closedconnectDB() does not signal connection problems to scheduler
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2012-09-25
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
4.7
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
I had the case that the credentials in localconf.php where dependent on an environment-variable. Not passing this variable to scheduler resulted in failing connections to the database (obviously) but the scheduler didn't tell any problems except for the return code 1 instead of 0.
This could be easier…
The thrown exceptions do not show in the cli-environment, therefor a switch could be added to use a die($message) when in cli-mode.
Actions