Bug #81049
closedNot possible to use different DB connection for tables, defined in TCA due to Reference Index
100%
Description
Hi,
I'm really excited about the feature, which allows separation of tables with different databases.
But actually I'm unable to use it for any table, which has TCA definition. As soon as such a table appears in a different Connection and record is saved in BE, I'm getting:
An exception occurred while executing 'SELECT `uid` FROM `tabalename` WHERE `uid` = ?' with params [1]: Table 'db-name.tablename' doesn't exist
Stacktrace shows the problem:
TYPO3\CMS\Core\DataHandling\DataHandler::updateRefIndex("tablename", 1)
The record itself is saved in separate DB and is accessible in BE lists and edit form, but any save in BE brings this exception.
Looking at the code I can say, that problem is in ReferenceIndex reusing the Connection object, but not sure if it is done for purpose or just a bug?
Updated by Morton Jonuschat over 7 years ago
- Category set to Backend API
- Status changed from New to Accepted
- Assignee set to Morton Jonuschat
- Target version set to next-patchlevel
Updated by Gerrit Code Review over 7 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53131
Updated by Gerrit Code Review over 7 years ago
Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53144
Updated by Morton Jonuschat over 7 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 2da4e3d2b3b094b92b277a3365beadeab81c0974.