Skip to content

feat: Add SQL migration script for new proposal statuses

Edouard Legoupil requested to merge feat-add-migration-script into main_dev

Created by: Edouard-Legoupil

This commit adds a new SQL migration script to update existing databases with the proposal_status_new enum. This script is idempotent and can be safely run multiple times.

The script:

  • Creates the proposal_status_new enum if it doesn't exist.

  • Alters the proposals, proposal_status_history, and knowledge_cards tables to use the new enum.

  • Drops the old proposal_status enum.

  • Does my code meet the quality standards for releasing packages?

  • Does the reviewer have all the information to validate the features/issues without too much research?

  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports