Project

General

Profile

Actions

Task #84100

closed

ConnectionPool::getConnectionByName() should not be marked as "internal"

Added by Stefan P about 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-03-01
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Currently this method is marked as internal and states that one should prefer to get the connection by table name. But there are valid (not-"edge") cases where one can not use the table name. For example, we have a project that exports data to foreign databases (which are not connected to our TYPO3 setup in any way). These databases are owned by different customers. These customers get a well-defined database scheme from us with the same(!) table names and columns - so we can not map a table name to a connection, but we map our external partners to connections. We use the ConnectionPool to manage the different database targets, but always get the "warning" while programming that this method is internal and should be avoided - which is pure cosmetic, admitedly, but still very wrong in our case.

Actions

Also available in: Atom PDF