Project

General

Profile

Actions
Copy link

User story #2363

closed

Add a datatable to store version information

Added by François ARMAND almost 13 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
2
Assignee:
Jonathan CLARKE
Category:
Packaging
Target version:
2.4.0~alpha6
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

We need to have a table to store information about the current version, as detected by the migration script.

That table would at least store the current XML "fileFormat" version.

Actions
Copy link
 #1

Updated by Jonathan CLARKE almost 13 years ago

  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES

Nicolas, can you create a SQL migration file in the rudder project, under rudder-core/src/main/resources/Migration, similar to the other ones, to add this table?

When it's done, don't close this bug, but re-assign it to me (or NPE or MCE, with their agreement) so that we can call the script from the rudder-upgrade script in packaging.

Thanks!

Actions
Copy link
 #2

Updated by François ARMAND almost 13 years ago

  • Status changed from 2 to In progress
  • Assignee changed from Nicolas CHARLES to François ARMAND
Actions
Copy link
 #3

Updated by François ARMAND almost 13 years ago

  • Status changed from In progress to Discussion
  • Assignee changed from François ARMAND to Jonathan CLARKE

I created the file rudder-core/src/main/resources/Migration/dbMigration-2.3-2.4-add-MigrationEventLog-table.sql in charge to add the new table.

I also modified rudder-core/src/main/resources/reportsSchema.sql to create that table for an installation from scratch - is that the good thing to do, or do we want to always use the migration scripts ?

Actions
Copy link
 #4

Updated by Matthieu CERDA over 12 years ago

  • Status changed from Discussion to Pending technical review
  • % Done changed from 0 to 100

Applied in changeset commit:797ccdbc3fcbd39f0785c7f06cf2f71d7f3782fb.

Actions
Copy link
 #5

Updated by Matthieu CERDA over 12 years ago

The migration scripts are only for migrations, during basic installations we should always rely on init files like rudder-core/src/main/resources/reportsSchema.sql. (my two cents)

Actions
Copy link
 #6

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from Pending technical review to 10

Looks good to me.

Actions
Copy link
 #7

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from 10 to Released

To clarify this from a functional point of view, it's one of the steps that allows an upgrade from Rudder 2.3 to 2.4 to keep event logs from the previous version, by converting them automatically.

Actions
Copy link
 #8

Updated by Nicolas PERRON almost 12 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions
Copy link
 #9

Updated by Benoît PECCATTE almost 10 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions
Copy link

Also available in: Atom PDF