Merge pull request #22 from dotkernel/issue-21

Issue #21: Added instructions to create migration

Author: alexmerlin

docs/book/v6/installation/doctrine-orm.md

@@ -5,12 +5,10 @@ We do not cover the creation steps of the database itself.
 
 ## Setup database
 
-Create a new MySQL database and set its collation to `utf8mb4_general_ci`.
+Create a new **MariaDB**/**MySQL** database and set its collation to `utf8mb4_general_ci`.
 
 Make sure you fill out the database credentials in `config/autoload/local.php` under `$databases['default']`.
-Below is the item you need to focus on.
-
-> `my_database`, `my_user`, `my_password` are provided only as an example.
+Below is the item you need to focus on:
 
 ```php
 $databases = [
@@ -28,41 +26,53 @@ $databases = [
 ];
 ```
 
-## Running migrations
+> `my_database`, `my_user`, `my_password` are provided only as an example.
+
+### Creating migrations
+
+Create a database migration by executing the following command:
+
+```shell
+php ./vendor/bin/doctrine-migrations diff
+```
+
+The new migration file will be placed in `src/Core/src/App/src/Migration/`.
 
-Run the database migrations by using the following command:
+### Running migrations
+
+Run the database migrations by executing the following command:
 
 ```shell
 php ./vendor/bin/doctrine-migrations migrate
 ```
 
-> If you have already run the migrations, you may get this message.
-> You should double-check to make sure the new migrations are ok to run.
+> If you have already run the migrations, you may get the below message:
 
 ```text
 WARNING! You have x previously executed migrations in the database that are not registered migrations.
   {migration list}
 Are you sure you wish to continue? (y/n)
 ```
 
-When using an empty database, you will get this confirmation message instead.
+> In this case, you should double-check to make sure the new migrations are ok to run.
+
+When using an empty database, you will get this confirmation message:
 
 ```text
 WARNING! You are about to execute a migration in database "<your_database_name>" that could result in schema changes and data loss. Are you sure you wish to continue? (yes/no)
 ```
 
-Again, submit `y` to run all the migrations in chronological order.
+Hit `Enter` to confirm the operation.
+This will run all the migrations in chronological order.
 Each migration will be logged in the `migrations` table to prevent running the same migration more than once, which is often not desirable.
 
 If everything ran correctly, you will get this confirmation.
 
 ```text
-[OK] Successfully migrated to version: Core\App\Migration\Version20250407142911
+[OK] Successfully migrated to version: Core\App\Migration\VersionYYYYMMDDHHMMSS
 ```
 
-> The migration name `Version20250407142911` may differ in future Admin updates.
-
-## Fixtures
+### Fixtures
 
 Run this command to populate the admin tables with the default values: