Project

General

Profile

Feature #1245

Move to (good) single-database mode

Added by Yannick Warnier over 9 years ago. Updated over 7 years ago.

Status:
Feature implemented
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
05/05/2010
Due date:
% Done:

100%

Estimated time:
200.00 h
Complexity:
Wizard-level
SCRUM pts - complexity:
100

Description

Having several databases have killed any attempt at having an easy installation process and have misleaded tons of people into believing that the current single-database mode is a better idea. This has to change.

The change to one single database implies unifying tables and adding a course_id field in every one of them (see #1244). This is a highly risky process, and automated tests should be put in place before development to ensure we don't loose features.

History

#1

Updated by Yannick Warnier about 9 years ago

  • Target version changed from 1.8.7.1 to 1.8.8 stable
#2

Updated by Yannick Warnier over 8 years ago

  • Target version changed from 1.8.8 stable to 1.9 Stable
#3

Updated by Julio Montoya over 7 years ago

  • Status changed from New to Feature implemented
  • % Done changed from 0 to 100

see #3910

Also available in: Atom PDF