Project

General

Profile

Actions
Copy link

Feature #4720

closed

Separate Database for Form & FormElement - Multi DB

Added by Carsten Rose almost 6 years ago. Updated over 5 years ago.

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

0%

Estimated time:
Discuss:
Prio Planung:

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'-DBNewCarsten Rose18.02.2018

Actions
Actions
Copy link
 #1

Updated by Carsten Rose almost 6 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #2

Updated by Carsten Rose almost 6 years ago

  • Target version changed from 0.23 to next7
Actions
Copy link
 #3

Updated by Carsten Rose over 5 years ago

  • Subject changed from Separate Database for Form & FormElement to Separate Database for Form & FormElement - Multi DB
Actions
Copy link
 #5

Updated by Carsten Rose over 5 years ago

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

Updated by Carsten Rose over 5 years ago

  • Status changed from In Progress to Closed
  • Target version deleted (next7)
Actions
Copy link

Also available in: Atom PDF