Project

General

Profile

Feature #4720

Separate Database for Form & FormElement - Multi DB

Added by Carsten Rose almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
05.10.2017
Due date:
% Done:

0%

Estimated time:
Discuss:

Description

In einigen Faellen ist es wuenschenswert wenn fuer 'Form' und 'FormElement' eine andere Datenbank genutzt werden koennte:

  • T3 Instanzen: Biostat, JES, my (QFQ)
  • Die Instanzen laufen mit unterschiedlichen QFQ Versionen - es wird schwierig immer alle auf der gleichen Version zu halten.

Related issues

Related to QFQ - Bug #5459: Multi DB: spread system tables between 'QFQ' and 'Data'-DBNew2018-02-18

Associated revisions

Revision 3dd24173
Added by Carsten Rose almost 3 years ago

Merge remote-tracking branch 'origin/Ticket4720-C-DifferentHandles'

  1. Conflicts:
  2. extension/qfq/qfq/database/Database.php
  3. extension/qfq/tests/phpunit/AbstractDatabaseTest.php

History

#1 Updated by Carsten Rose almost 3 years ago

  • Status changed from New to In Progress

#2 Updated by Carsten Rose almost 3 years ago

  • Target version changed from 0.23 to next2

#3 Updated by Carsten Rose over 2 years ago

  • Subject changed from Separate Database for Form & FormElement to Separate Database for Form & FormElement - Multi DB

#5 Updated by Carsten Rose over 2 years ago

  • Related to Bug #5459: Multi DB: spread system tables between 'QFQ' and 'Data'-DB added

#6 Updated by Carsten Rose over 2 years ago

  • Status changed from In Progress to Closed
  • Target version deleted (next2)

Also available in: Atom PDF