Skip to content

Commit 173034f

Browse files
author
Bizley
committed
better readme
1 parent 168ebe4 commit 173034f

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

README.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -78,19 +78,19 @@ Starting with yii2-migration v2.0 it is possible to generate updating migration
7878

7979
## Command line parameters
8080

81-
| --command | -alias | description | default value
82-
|----------------------|:------:|-------------------------------------------------------------------------|------------------------------------------------------------
83-
| `db` | | Application component's ID of the DB connection to use when generating migrations. | `'db'`
84-
| `migrationPath` | `p` | Directory storing the migration classes. | `'@app/migrations'`
85-
| `migrationNamespace` | `n` | Namespace in case of generating namespaced migration. | `null`
86-
| `templateFile` | `F` | Template file for generating create migrations. | `'@vendor/bizley/migration/src/views/create_migration.php'`
87-
| `templateFileUpdate` | `U` | Template file for generating update migrations. | `'@vendor/bizley/migration/src/views/update_migration.php'`
88-
| `useTablePrefix` | `P` | Whether the table names generated should consider the `tablePrefix` setting of the DB connection. | `1`
89-
| `migrationTable` | `t` | Name of the table for keeping applied migration information. | `'{{%migration}}'`
90-
| `showOnly` | `s` | Whether to only display changes instead of generating update migration. | `0`
91-
| `generalSchema` | `g` | Whether to use general column schema instead of database specific (1). | `0`
92-
| `fixHistory` | `h` | Whether to add migration history entry when migration is generated. | `0`
93-
| `skipMigrations` | | List of migrations from the history table that should be skipped during the update process. (2) | `[]`
81+
| --command | -alias | description
82+
|----------------------|:------:|-----------------------------------------------------------------------------------------------------------------------
83+
| `db` | | Application component's ID of the DB connection to use when generating migrations. _default:_ `'db'`
84+
| `migrationPath` | `p` | Directory storing the migration classes. _default:_ `'@app/migrations'`
85+
| `migrationNamespace` | `n` | Namespace in case of generating namespaced migration. _default:_ `null`
86+
| `templateFile` | `F` | Template file for generating create migrations. _default:_ `'@vendor/bizley/migration/src/views/create_migration.php'`
87+
| `templateFileUpdate` | `U` | Template file for generating update migrations. _default:_ `'@vendor/bizley/migration/src/views/update_migration.php'`
88+
| `useTablePrefix` | `P` | Whether the table names generated should consider the `tablePrefix` setting of the DB connection. _default:_ `1`
89+
| `migrationTable` | `t` | Name of the table for keeping applied migration information. _default:_ `'{{%migration}}'`
90+
| `showOnly` | `s` | Whether to only display changes instead of generating update migration. _default:_ `0`
91+
| `generalSchema` | `g` | Whether to use general column schema instead of database specific (1). _default:_ `0`
92+
| `fixHistory` | `h` | Whether to add migration history entry when migration is generated. _default:_ `0`
93+
| `skipMigrations` | | List of migrations from the history table that should be skipped during the update process (2). _default:_ `[]`
9494

9595
(1) Remember that with different database types general column schemas may be generated with different length.
9696

0 commit comments

Comments
 (0)