Bug #81049

Not possible to use different DB connection for tables, defined in TCA due to Reference Index

Added by Viktor Livakivskyi over 4 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Should have
Category:
Backend API
Target version:
Start date:
2017-04-27
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

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?

#1

Updated by Morton Jonuschat over 4 years ago

  • Category set to Backend API
  • Status changed from New to Accepted
  • Assignee set to Morton Jonuschat
  • Target version set to next-patchlevel
#2

Updated by Gerrit Code Review over 4 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

#3

Updated by Gerrit Code Review over 4 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

#4

Updated by Morton Jonuschat over 4 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#5

Updated by Benni Mack almost 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF