So i completely understand and know that migrations shouldn't be used to seed data. That being said I have a migration that does just that. My question is regarding the beginTransaction aspects. Are there any pitfalls or edge cases that I should watch out for when it comes to wrapping up and down methods in a migration with beginTransaction?public function up()    {        DB::beginTransaction();        DB::table('SomeTable')->where([            'companyId' => 111,            'indicatorName' => 'level1'        ])->update([            'fieldUnit' => 'PERCENTAGE'        ]);        DB::commit();    }    /**     * Reverse the migrations.     *     * @return void     */    public function down()    {         DB::beginTransaction();        DB::table('SomeTable')->where([            'companyId' => 111,            'indicatorName' => 'level1'        ])->update([            'fieldUnit' => 'CURRENCY'        ]);        DB::commit();    }
Laravel Migrations & Transactions
php;laravel