diff --git a/docs/update_and_migration/from_3.3/update_from_3.3.md b/docs/update_and_migration/from_3.3/update_from_3.3.md index aed320dc41..6ecfa69aa0 100644 --- a/docs/update_and_migration/from_3.3/update_from_3.3.md +++ b/docs/update_and_migration/from_3.3/update_from_3.3.md @@ -422,6 +422,11 @@ Run the following scripts: psql < vendor/ibexa/installer/upgrade/db/postgresql/ibexa-3.3.33-to-3.3.34.sql ``` -### v3.3.40 +### v3.3.41 -A command to deal with duplicated database entries, as reported in [IBX-8562](https://issues.ibexa.co/browse/IBX-8562), will be available soon. \ No newline at end of file +Run the command to deal with duplicated database entries (as reported in [IBX-8562](https://issues.ibexa.co/browse/IBX-8562)). + +First, take a look at the available options for this command by running `php bin/console help ibexa:content:remove-duplicate-fields`. +For example, to not overload the database, treatment can be devided into batches with a delay between them. + +TODO: Any advice about running this in production? On Ibexa Cloud? diff --git a/docs/update_and_migration/from_4.5/update_from_4.5.md b/docs/update_and_migration/from_4.5/update_from_4.5.md index 0947d9b97c..1684dfd14a 100644 --- a/docs/update_and_migration/from_4.5/update_from_4.5.md +++ b/docs/update_and_migration/from_4.5/update_from_4.5.md @@ -518,10 +518,6 @@ composer dump-autoload No additional steps needed. -## v4.6.10 - -A command to deal with duplicated database entries, as reported in [IBX-8562](https://issues.ibexa.co/browse/IBX-8562), will be available soon. - ## v4.6.11 ### Ibexa Cloud @@ -536,3 +532,12 @@ composer ibexa:setup --platformsh Review the changes applied to `.platform.app.yaml` and `.platform/`, merge with your custom settings if needed, and commit them to Git. + +## v4.6.12 + +Run the command to deal with duplicated database entries (as reported in [IBX-8562](https://issues.ibexa.co/browse/IBX-8562)). + +First, take a look at the available options for this command by running `php bin/console help ibexa:content:remove-duplicate-fields`. +For example, to not overload the database, treatment can be devided into batches with a delay between them. + +TODO: Any advice about running this in production? On Ibexa Cloud?