Task #84100
closedConnectionPool::getConnectionByName() should not be marked as "internal"
100%
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.