|
23 | 23 | | the migration records for consistency so the output file can be managed
|
24 | 24 | | in source control.
|
25 | 25 | |
|
26 |
| - | If the order migrations are applied will produce significant differences, |
27 |
| - | such as changing the behavior of the app, then this should be left |
28 |
| - | disabled. In such cases `migrate:fresh --database=test` followed by |
29 |
| - | `migrate` or `migrate:dump` can achieve similar consistency. |
| 26 | + | If the order that closely versioned migrations are applied will produce |
| 27 | + | significant differences, such as changing the behavior of the app, then |
| 28 | + | disabling this may be preferred. |
30 | 29 | |
|
31 | 30 | */
|
32 | 31 |
|
33 |
| - 'reorder' => env('MIGRATION_SNAPSHOT_REORDER', false), |
| 32 | + 'reorder' => env('MIGRATION_SNAPSHOT_REORDER', true), |
34 | 33 |
|
35 | 34 | /*
|
36 | 35 | |--------------------------------------------------------------------------
|
37 |
| - | Whether to trim underscores from foreign constraints for consistency. |
| 36 | + | Whether to trim leading underscores from foreign constraints. |
38 | 37 | |--------------------------------------------------------------------------
|
39 | 38 | |
|
40 | 39 | | Percona's Online Schema Change for Mysql may prepend foreign constraints
|
41 | 40 | | with underscores. Since it may not be used in all environments some dumped
|
42 | 41 | | snapshots may not match, adding unnecessary noise to source control.
|
43 |
| - | Enable this trimming to get more consistent snapshots when PTOSC may be |
44 |
| - | used. |
| 42 | + | Disable this trimming if leading underscores are significant for your use |
| 43 | + | case. |
45 | 44 | |
|
46 | 45 | */
|
47 |
| - 'trim-underscores' => env('MIGRATION_SNAPSHOT_TRIM_UNDERSCORES', false), |
| 46 | + 'trim-underscores' => env('MIGRATION_SNAPSHOT_TRIM_UNDERSCORES', true), |
48 | 47 | ];
|
0 commit comments