Project

General

Profile

Support #7423

DB change list

Added by Julio Montoya almost 5 years ago. Updated about 4 years ago.

Status:
Feature implemented
Priority:
Normal
Category:
-
Target version:
Start date:
25/11/2014
Due date:
% Done:

100%

Estimated time:
Complexity:
Normal
SCRUM pts - complexity:
?

Description

List of features that requires DB changes.

History

#2

Updated by Yannick Warnier about 4 years ago

I'm removing #7431 from the list because it will not be implemented in 1.10.0

#3

Updated by Yannick Warnier about 4 years ago

  • Tracker changed from Feature to Support
#4

Updated by Yannick Warnier about 4 years ago

  • Status changed from Assigned to Needs more info
  • Assignee changed from Yannick Warnier to Julio Montoya
  • % Done changed from 0 to 50

I think we should close this task. Thanks to the migrations, we now have a clearer idea of what changes were done when.

Any thought?

#5

Updated by Julio Montoya about 4 years ago

  • Assignee changed from Julio Montoya to Yannick Warnier

Yannick Warnier wrote:

I think we should close this task. Thanks to the migrations, we now have a clearer idea of what changes were done when.

Any thought?

I think we don't have to update every time this value in the DB "chamilo_database_version".

#6

Updated by Yannick Warnier about 4 years ago

  • Assignee changed from Yannick Warnier to Julio Montoya

If we don't do it, we still don't know exactly what would be changed in the data, right?
Is there a way through which we could ensure that both installs and upgrades maintain the exact same database version (be it the chamilo_database_version or the "version" table) before we release 1.10.0?

#7

Updated by Julio Montoya about 4 years ago

  • Assignee changed from Julio Montoya to Yannick Warnier

Yannick Warnier wrote:

If we don't do it, we still don't know exactly what would be changed in the data, right?
Is there a way through which we could ensure that both installs and upgrades maintain the exact same database version (be it the chamilo_database_version or the "version" table) before we release 1.10.0?

Ahhh "data" well yes there's a solution for that but it will take some time to implement "doctrine fixtures".
So let's stick with "chamilo_database_version". One more thing: the version should be the same as in the name of the migration file.

Example: migration file: Version20150706135000.php for chamilo_database_version "20150706135000".

#8

Updated by Yannick Warnier about 4 years ago

  • Status changed from Needs more info to Feature implemented
  • % Done changed from 50 to 100

OK.

Also available in: Atom PDF