migration
This commit is contained in:
@@ -15,9 +15,11 @@ const NEW_NOTIFICATION_KEYS = [NotificationScenarioKey.DEPOSIT_RECEIPT_SUBMITTED
|
||||
* Only adds the new enum values. Postgres forbids using a newly added enum
|
||||
* value in the same transaction it was created in, so seeding the actual
|
||||
* scenario rows is handled by the follow-up `SeedDepositScenarios` migration.
|
||||
* `transaction = false` commits ADD VALUE immediately (required by Postgres).
|
||||
*/
|
||||
export class AddDepositScenarios1722000000000 implements MigrationInterface {
|
||||
name = 'AddDepositScenarios1722000000000';
|
||||
transaction = false;
|
||||
|
||||
public async up(queryRunner: QueryRunner): Promise<void> {
|
||||
for (const key of NEW_SMS_KEYS) {
|
||||
|
||||
Reference in New Issue
Block a user