Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update database 9.x #1934

Merged
merged 2 commits into from
Feb 26, 2025

Conversation

M0rgan01
Copy link
Contributor

@M0rgan01 M0rgan01 commented Feb 25, 2025

Questions Answers
Branch? 9.x temp
Description? Update database section / Fix CLI section
Fixed ticket? -

Copy link

@tblivet tblivet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Modifier les occurence de la v8 exemple:

  • (8.0.x releases example)
  • 8.0.0
  • ps_800
  • ...


### Defining changes

Once PrestaShop is installed, the default structure and content files we saw are not used anymore.

If a new release of PrestaShop must bring changes to the existing database, an upgrade file must be created along the `db_structure.sql` update.
If a new release of PrestaShop must bring changes to the existing database, an update file must be created along the `db_structure.sql` update.
This SQL file will be stored in the [auto upgrade](https://github.com/PrestaShop/autoupgrade/tree/dev/upgrade/sql) module in the folder `/upgrade/sql/`.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This SQL file will be stored in the [auto upgrade](https://github.com/PrestaShop/autoupgrade/tree/dev/upgrade/sql) module in the folder `/upgrade/sql/`.
This SQL file will be stored in the [update assistant](https://github.com/PrestaShop/autoupgrade/tree/dev/upgrade/sql) module in the folder `/upgrade/sql/`.

@M0rgan01 M0rgan01 merged commit 197f0ae into PrestaShop:9.x-temp-autoupdate Feb 26, 2025
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants