Project

General

Profile

Actions
Copy link

Bug #81049

closed

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

Added by Viktor Livakivskyi almost 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Morton Jonuschat
Category:
Backend API
Target version:
next-patchlevel
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?

Actions
Copy link

Also available in: Atom PDF