@dynamatix/gb-schemas 2.0.30 → 2.0.31

package/prisma/migrations/20250501102630_job_setting_name_change/migration.sql

@@ -1,10 +1,10 @@
-/*
-  Warnings:
-
-  - You are about to drop the column `job_name` on the `job_settings` table. All the data in the column will be lost.
-  - Added the required column `name` to the `job_settings` table without a default value. This is not possible if the table is not empty.
-
-*/
--- AlterTable
-ALTER TABLE "job_settings" DROP COLUMN "job_name",
-ADD COLUMN     "name" TEXT NOT NULL;
+/*
+  Warnings:
+
+  - You are about to drop the column `job_name` on the `job_settings` table. All the data in the column will be lost.
+  - Added the required column `name` to the `job_settings` table without a default value. This is not possible if the table is not empty.
+
+*/
+-- AlterTable
+ALTER TABLE "job_settings" DROP COLUMN "job_name",
+ADD COLUMN     "name" TEXT NOT NULL;

package/prisma/migrations/20250501104920_milstone_update/migration.sql

@@ -1,30 +1,30 @@
-/*
-  Warnings:
-
-  - You are about to drop the column `completed_at` on the `apprivo_sync_journeys` table. All the data in the column will be lost.
-  - You are about to drop the column `journey_id` on the `apprivo_sync_journeys` table. All the data in the column will be lost.
-  - You are about to drop the column `started_at` on the `apprivo_sync_journeys` table. All the data in the column will be lost.
-  - You are about to drop the column `status` on the `apprivo_sync_journeys` table. All the data in the column will be lost.
-  - Added the required column `application_id` to the `apprivo_sync_journeys` table without a default value. This is not possible if the table is not empty.
-  - Added the required column `is_first_pull` to the `apprivo_sync_journeys` table without a default value. This is not possible if the table is not empty.
-  - Added the required column `milestone_status` to the `apprivo_sync_journeys` table without a default value. This is not possible if the table is not empty.
-
-*/
--- AlterTable
-ALTER TABLE "apprivo_sync_journeys" DROP COLUMN "completed_at",
-DROP COLUMN "journey_id",
-DROP COLUMN "started_at",
-DROP COLUMN "status",
-ADD COLUMN     "application_id" TEXT NOT NULL,
-ADD COLUMN     "end_time" TIMESTAMP(3),
-ADD COLUMN     "is_first_pull" TEXT NOT NULL,
-ADD COLUMN     "job_run_id" TEXT,
-ADD COLUMN     "milestone_lid" TEXT,
-ADD COLUMN     "milestone_status" TEXT NOT NULL,
-ADD COLUMN     "start_time" TIMESTAMP(3);
-
--- AddForeignKey
-ALTER TABLE "apprivo_sync_journeys" ADD CONSTRAINT "apprivo_sync_journeys_milestone_lid_fkey" FOREIGN KEY ("milestone_lid") REFERENCES "lookups"("id") ON DELETE SET NULL ON UPDATE CASCADE;
-
--- AddForeignKey
-ALTER TABLE "apprivo_sync_journeys" ADD CONSTRAINT "apprivo_sync_journeys_job_run_id_fkey" FOREIGN KEY ("job_run_id") REFERENCES "job_runs"("id") ON DELETE SET NULL ON UPDATE CASCADE;
+/*
+  Warnings:
+
+  - You are about to drop the column `completed_at` on the `apprivo_sync_journeys` table. All the data in the column will be lost.
+  - You are about to drop the column `journey_id` on the `apprivo_sync_journeys` table. All the data in the column will be lost.
+  - You are about to drop the column `started_at` on the `apprivo_sync_journeys` table. All the data in the column will be lost.
+  - You are about to drop the column `status` on the `apprivo_sync_journeys` table. All the data in the column will be lost.
+  - Added the required column `application_id` to the `apprivo_sync_journeys` table without a default value. This is not possible if the table is not empty.
+  - Added the required column `is_first_pull` to the `apprivo_sync_journeys` table without a default value. This is not possible if the table is not empty.
+  - Added the required column `milestone_status` to the `apprivo_sync_journeys` table without a default value. This is not possible if the table is not empty.
+
+*/
+-- AlterTable
+ALTER TABLE "apprivo_sync_journeys" DROP COLUMN "completed_at",
+DROP COLUMN "journey_id",
+DROP COLUMN "started_at",
+DROP COLUMN "status",
+ADD COLUMN     "application_id" TEXT NOT NULL,
+ADD COLUMN     "end_time" TIMESTAMP(3),
+ADD COLUMN     "is_first_pull" TEXT NOT NULL,
+ADD COLUMN     "job_run_id" TEXT,
+ADD COLUMN     "milestone_lid" TEXT,
+ADD COLUMN     "milestone_status" TEXT NOT NULL,
+ADD COLUMN     "start_time" TIMESTAMP(3);
+
+-- AddForeignKey
+ALTER TABLE "apprivo_sync_journeys" ADD CONSTRAINT "apprivo_sync_journeys_milestone_lid_fkey" FOREIGN KEY ("milestone_lid") REFERENCES "lookups"("id") ON DELETE SET NULL ON UPDATE CASCADE;
+
+-- AddForeignKey
+ALTER TABLE "apprivo_sync_journeys" ADD CONSTRAINT "apprivo_sync_journeys_job_run_id_fkey" FOREIGN KEY ("job_run_id") REFERENCES "job_runs"("id") ON DELETE SET NULL ON UPDATE CASCADE;

package/prisma/migrations/20250501105546_apprivo_sync_journey_update/migration.sql

@@ -1,9 +1,9 @@
-/*
-  Warnings:
-
-  - Changed the type of `is_first_pull` on the `apprivo_sync_journeys` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-
-*/
--- AlterTable
-ALTER TABLE "apprivo_sync_journeys" DROP COLUMN "is_first_pull",
-ADD COLUMN     "is_first_pull" BOOLEAN NOT NULL;
+/*
+  Warnings:
+
+  - Changed the type of `is_first_pull` on the `apprivo_sync_journeys` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+
+*/
+-- AlterTable
+ALTER TABLE "apprivo_sync_journeys" DROP COLUMN "is_first_pull",
+ADD COLUMN     "is_first_pull" BOOLEAN NOT NULL;

package/prisma/migrations/20250501105850_job_run_update/migration.sql

@@ -1,13 +1,13 @@
-/*
-  Warnings:
-
-  - You are about to drop the column `completed_at` on the `job_runs` table. All the data in the column will be lost.
-  - You are about to drop the column `started_at` on the `job_runs` table. All the data in the column will be lost.
-
-*/
--- AlterTable
-ALTER TABLE "job_runs" DROP COLUMN "completed_at",
-DROP COLUMN "started_at",
-ADD COLUMN     "end_time" TIMESTAMP(3),
-ADD COLUMN     "error" TEXT,
-ADD COLUMN     "start_time" TIMESTAMP(3);
+/*
+  Warnings:
+
+  - You are about to drop the column `completed_at` on the `job_runs` table. All the data in the column will be lost.
+  - You are about to drop the column `started_at` on the `job_runs` table. All the data in the column will be lost.
+
+*/
+-- AlterTable
+ALTER TABLE "job_runs" DROP COLUMN "completed_at",
+DROP COLUMN "started_at",
+ADD COLUMN     "end_time" TIMESTAMP(3),
+ADD COLUMN     "error" TEXT,
+ADD COLUMN     "start_time" TIMESTAMP(3);

package/prisma/migrations/20250505115236_update_application_schema/migration.sql

@@ -1,115 +1,115 @@
-/*
-  Warnings:
-
-  - You are about to drop the column `application_status_lid` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `application_sub_type_lid` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `application_sub_type_other` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `application_sub_type_other_details` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `application_sub_type_other_lid` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `application_sub_type_other_lid_details` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `application_sub_type_other_lid_other` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `application_sub_type_other_lid_other_details` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `created_at` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `pageValidFlag` on the `applications` table. All the data in the column will be lost.
-  - You are about to drop the column `updated_at` on the `applications` table. All the data in the column will be lost.
-  - The `case_manager_accepted` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - The `is_broker_assigned` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - The `last_updated` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - The `submitted_date` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - The `is_active` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - The `is_uk_resident` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - Changed the type of `is_application_fee_paid` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-  - Changed the type of `is_intend_to_occupy` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-  - Changed the type of `is_introducer_submission` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-  - Changed the type of `is_finance_recommended_to_applicant` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-  - Changed the type of `is_workflow_task_created` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-  - Changed the type of `is_network_club_submission` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-  - Changed the type of `is_valuation_fee_paid` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-
-*/
--- DropForeignKey
-ALTER TABLE "applications" DROP CONSTRAINT "applications_broker_id_fkey";
-
--- DropIndex
-DROP INDEX "applications_company_id_key";
-
--- DropIndex
-DROP INDEX "applications_direct_debit_id_key";
-
--- DropIndex
-DROP INDEX "applications_mortgage_id_key";
-
--- DropIndex
-DROP INDEX "applications_rationale_id_key";
-
--- DropIndex
-DROP INDEX "applications_security_id_key";
-
--- DropIndex
-DROP INDEX "applications_solicitor_id_key";
-
--- AlterTable
-ALTER TABLE "applications" DROP COLUMN "application_status_lid",
-DROP COLUMN "application_sub_type_lid",
-DROP COLUMN "application_sub_type_other",
-DROP COLUMN "application_sub_type_other_details",
-DROP COLUMN "application_sub_type_other_lid",
-DROP COLUMN "application_sub_type_other_lid_details",
-DROP COLUMN "application_sub_type_other_lid_other",
-DROP COLUMN "application_sub_type_other_lid_other_details",
-DROP COLUMN "created_at",
-DROP COLUMN "pageValidFlag",
-DROP COLUMN "updated_at",
-ADD COLUMN     "applicant_ids" TEXT[],
-DROP COLUMN "is_application_fee_paid",
-ADD COLUMN     "is_application_fee_paid" BOOLEAN NOT NULL,
-ALTER COLUMN "broker_id" DROP NOT NULL,
-DROP COLUMN "case_manager_accepted",
-ADD COLUMN     "case_manager_accepted" BOOLEAN NOT NULL DEFAULT false,
-DROP COLUMN "is_intend_to_occupy",
-ADD COLUMN     "is_intend_to_occupy" BOOLEAN NOT NULL,
-DROP COLUMN "is_introducer_submission",
-ADD COLUMN     "is_introducer_submission" BOOLEAN NOT NULL,
-DROP COLUMN "is_broker_assigned",
-ADD COLUMN     "is_broker_assigned" BOOLEAN NOT NULL DEFAULT false,
-DROP COLUMN "is_finance_recommended_to_applicant",
-ADD COLUMN     "is_finance_recommended_to_applicant" BOOLEAN NOT NULL,
-DROP COLUMN "is_workflow_task_created",
-ADD COLUMN     "is_workflow_task_created" BOOLEAN NOT NULL,
-DROP COLUMN "last_updated",
-ADD COLUMN     "last_updated" TIMESTAMP(3),
-DROP COLUMN "is_network_club_submission",
-ADD COLUMN     "is_network_club_submission" BOOLEAN NOT NULL,
-DROP COLUMN "submitted_date",
-ADD COLUMN     "submitted_date" TIMESTAMP(3),
-DROP COLUMN "is_valuation_fee_paid",
-ADD COLUMN     "is_valuation_fee_paid" BOOLEAN NOT NULL,
-ALTER COLUMN "security_id" DROP NOT NULL,
-ALTER COLUMN "solicitor_id" DROP NOT NULL,
-DROP COLUMN "is_active",
-ADD COLUMN     "is_active" BOOLEAN NOT NULL DEFAULT false,
-DROP COLUMN "is_uk_resident",
-ADD COLUMN     "is_uk_resident" BOOLEAN NOT NULL DEFAULT true;
-
--- CreateTable
-CREATE TABLE "_SourceOfWealth" (
-    "A" TEXT NOT NULL,
-    "B" TEXT NOT NULL,
-
-    CONSTRAINT "_SourceOfWealth_AB_pkey" PRIMARY KEY ("A","B")
-);
-
--- CreateIndex
-CREATE INDEX "_SourceOfWealth_B_index" ON "_SourceOfWealth"("B");
-
--- CreateIndex
-CREATE INDEX "applications_source_of_wealth_lids_idx" ON "applications"("source_of_wealth_lids");
-
--- AddForeignKey
-ALTER TABLE "applications" ADD CONSTRAINT "applications_broker_id_fkey" FOREIGN KEY ("broker_id") REFERENCES "brokers"("id") ON DELETE SET NULL ON UPDATE CASCADE;
-
--- AddForeignKey
-ALTER TABLE "_SourceOfWealth" ADD CONSTRAINT "_SourceOfWealth_A_fkey" FOREIGN KEY ("A") REFERENCES "applications"("id") ON DELETE CASCADE ON UPDATE CASCADE;
-
--- AddForeignKey
-ALTER TABLE "_SourceOfWealth" ADD CONSTRAINT "_SourceOfWealth_B_fkey" FOREIGN KEY ("B") REFERENCES "lookups"("id") ON DELETE CASCADE ON UPDATE CASCADE;
+/*
+  Warnings:
+
+  - You are about to drop the column `application_status_lid` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `application_sub_type_lid` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `application_sub_type_other` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `application_sub_type_other_details` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `application_sub_type_other_lid` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `application_sub_type_other_lid_details` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `application_sub_type_other_lid_other` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `application_sub_type_other_lid_other_details` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `created_at` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `pageValidFlag` on the `applications` table. All the data in the column will be lost.
+  - You are about to drop the column `updated_at` on the `applications` table. All the data in the column will be lost.
+  - The `case_manager_accepted` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - The `is_broker_assigned` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - The `last_updated` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - The `submitted_date` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - The `is_active` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - The `is_uk_resident` column on the `applications` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - Changed the type of `is_application_fee_paid` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+  - Changed the type of `is_intend_to_occupy` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+  - Changed the type of `is_introducer_submission` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+  - Changed the type of `is_finance_recommended_to_applicant` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+  - Changed the type of `is_workflow_task_created` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+  - Changed the type of `is_network_club_submission` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+  - Changed the type of `is_valuation_fee_paid` on the `applications` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+
+*/
+-- DropForeignKey
+ALTER TABLE "applications" DROP CONSTRAINT "applications_broker_id_fkey";
+
+-- DropIndex
+DROP INDEX "applications_company_id_key";
+
+-- DropIndex
+DROP INDEX "applications_direct_debit_id_key";
+
+-- DropIndex
+DROP INDEX "applications_mortgage_id_key";
+
+-- DropIndex
+DROP INDEX "applications_rationale_id_key";
+
+-- DropIndex
+DROP INDEX "applications_security_id_key";
+
+-- DropIndex
+DROP INDEX "applications_solicitor_id_key";
+
+-- AlterTable
+ALTER TABLE "applications" DROP COLUMN "application_status_lid",
+DROP COLUMN "application_sub_type_lid",
+DROP COLUMN "application_sub_type_other",
+DROP COLUMN "application_sub_type_other_details",
+DROP COLUMN "application_sub_type_other_lid",
+DROP COLUMN "application_sub_type_other_lid_details",
+DROP COLUMN "application_sub_type_other_lid_other",
+DROP COLUMN "application_sub_type_other_lid_other_details",
+DROP COLUMN "created_at",
+DROP COLUMN "pageValidFlag",
+DROP COLUMN "updated_at",
+ADD COLUMN     "applicant_ids" TEXT[],
+DROP COLUMN "is_application_fee_paid",
+ADD COLUMN     "is_application_fee_paid" BOOLEAN NOT NULL,
+ALTER COLUMN "broker_id" DROP NOT NULL,
+DROP COLUMN "case_manager_accepted",
+ADD COLUMN     "case_manager_accepted" BOOLEAN NOT NULL DEFAULT false,
+DROP COLUMN "is_intend_to_occupy",
+ADD COLUMN     "is_intend_to_occupy" BOOLEAN NOT NULL,
+DROP COLUMN "is_introducer_submission",
+ADD COLUMN     "is_introducer_submission" BOOLEAN NOT NULL,
+DROP COLUMN "is_broker_assigned",
+ADD COLUMN     "is_broker_assigned" BOOLEAN NOT NULL DEFAULT false,
+DROP COLUMN "is_finance_recommended_to_applicant",
+ADD COLUMN     "is_finance_recommended_to_applicant" BOOLEAN NOT NULL,
+DROP COLUMN "is_workflow_task_created",
+ADD COLUMN     "is_workflow_task_created" BOOLEAN NOT NULL,
+DROP COLUMN "last_updated",
+ADD COLUMN     "last_updated" TIMESTAMP(3),
+DROP COLUMN "is_network_club_submission",
+ADD COLUMN     "is_network_club_submission" BOOLEAN NOT NULL,
+DROP COLUMN "submitted_date",
+ADD COLUMN     "submitted_date" TIMESTAMP(3),
+DROP COLUMN "is_valuation_fee_paid",
+ADD COLUMN     "is_valuation_fee_paid" BOOLEAN NOT NULL,
+ALTER COLUMN "security_id" DROP NOT NULL,
+ALTER COLUMN "solicitor_id" DROP NOT NULL,
+DROP COLUMN "is_active",
+ADD COLUMN     "is_active" BOOLEAN NOT NULL DEFAULT false,
+DROP COLUMN "is_uk_resident",
+ADD COLUMN     "is_uk_resident" BOOLEAN NOT NULL DEFAULT true;
+
+-- CreateTable
+CREATE TABLE "_SourceOfWealth" (
+    "A" TEXT NOT NULL,
+    "B" TEXT NOT NULL,
+
+    CONSTRAINT "_SourceOfWealth_AB_pkey" PRIMARY KEY ("A","B")
+);
+
+-- CreateIndex
+CREATE INDEX "_SourceOfWealth_B_index" ON "_SourceOfWealth"("B");
+
+-- CreateIndex
+CREATE INDEX "applications_source_of_wealth_lids_idx" ON "applications"("source_of_wealth_lids");
+
+-- AddForeignKey
+ALTER TABLE "applications" ADD CONSTRAINT "applications_broker_id_fkey" FOREIGN KEY ("broker_id") REFERENCES "brokers"("id") ON DELETE SET NULL ON UPDATE CASCADE;
+
+-- AddForeignKey
+ALTER TABLE "_SourceOfWealth" ADD CONSTRAINT "_SourceOfWealth_A_fkey" FOREIGN KEY ("A") REFERENCES "applications"("id") ON DELETE CASCADE ON UPDATE CASCADE;
+
+-- AddForeignKey
+ALTER TABLE "_SourceOfWealth" ADD CONSTRAINT "_SourceOfWealth_B_fkey" FOREIGN KEY ("B") REFERENCES "lookups"("id") ON DELETE CASCADE ON UPDATE CASCADE;

package/prisma/migrations/20250505145328_update_broker_schema/migration.sql

@@ -1,8 +1,8 @@
-/*
-  Warnings:
-
-  - Added the required column `application_id` to the `brokers` table without a default value. This is not possible if the table is not empty.
-
-*/
--- AlterTable
-ALTER TABLE "brokers" ADD COLUMN     "application_id" TEXT NOT NULL;
+/*
+  Warnings:
+
+  - Added the required column `application_id` to the `brokers` table without a default value. This is not possible if the table is not empty.
+
+*/
+-- AlterTable
+ALTER TABLE "brokers" ADD COLUMN     "application_id" TEXT NOT NULL;

package/prisma/migrations/20250505185034_update_direct_debit_schema/migration.sql

@@ -1,27 +1,27 @@
-/*
-  Warnings:
-
-  - Added the required column `branch` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
-  - Added the required column `contact_postcode` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
-  - Added the required column `is_confirm_declaration` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
-  - Added the required column `name_of_account_holder` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
-  - Added the required column `selected_payment_day_lid` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
-  - Changed the type of `account_number` on the `application_direct_debits` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-  - Changed the type of `sort_code` on the `application_direct_debits` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
-
-*/
--- AlterTable
-ALTER TABLE "application_direct_debits" ADD COLUMN     "address_line1" TEXT,
-ADD COLUMN     "address_line2" TEXT,
-ADD COLUMN     "applicant_id" TEXT,
-ADD COLUMN     "branch" TEXT NOT NULL,
-ADD COLUMN     "city" TEXT,
-ADD COLUMN     "contact_postcode" TEXT NOT NULL,
-ADD COLUMN     "institution" TEXT,
-ADD COLUMN     "is_confirm_declaration" BOOLEAN NOT NULL,
-ADD COLUMN     "name_of_account_holder" TEXT NOT NULL,
-ADD COLUMN     "selected_payment_day_lid" TEXT NOT NULL,
-DROP COLUMN "account_number",
-ADD COLUMN     "account_number" INTEGER NOT NULL,
-DROP COLUMN "sort_code",
-ADD COLUMN     "sort_code" INTEGER NOT NULL;
+/*
+  Warnings:
+
+  - Added the required column `branch` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
+  - Added the required column `contact_postcode` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
+  - Added the required column `is_confirm_declaration` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
+  - Added the required column `name_of_account_holder` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
+  - Added the required column `selected_payment_day_lid` to the `application_direct_debits` table without a default value. This is not possible if the table is not empty.
+  - Changed the type of `account_number` on the `application_direct_debits` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+  - Changed the type of `sort_code` on the `application_direct_debits` table. No cast exists, the column would be dropped and recreated, which cannot be done if there is data, since the column is required.
+
+*/
+-- AlterTable
+ALTER TABLE "application_direct_debits" ADD COLUMN     "address_line1" TEXT,
+ADD COLUMN     "address_line2" TEXT,
+ADD COLUMN     "applicant_id" TEXT,
+ADD COLUMN     "branch" TEXT NOT NULL,
+ADD COLUMN     "city" TEXT,
+ADD COLUMN     "contact_postcode" TEXT NOT NULL,
+ADD COLUMN     "institution" TEXT,
+ADD COLUMN     "is_confirm_declaration" BOOLEAN NOT NULL,
+ADD COLUMN     "name_of_account_holder" TEXT NOT NULL,
+ADD COLUMN     "selected_payment_day_lid" TEXT NOT NULL,
+DROP COLUMN "account_number",
+ADD COLUMN     "account_number" INTEGER NOT NULL,
+DROP COLUMN "sort_code",
+ADD COLUMN     "sort_code" INTEGER NOT NULL;

package/prisma/migrations/20250505190613_update_solicitor_schema/migration.sql

@@ -1,29 +1,29 @@
-/*
-  Warnings:
-
-  - The `sort_code` column on the `solicitors` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - Made the column `address_country_lid` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
-  - Made the column `address_line1` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
-  - Made the column `address_post_code` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
-  - Made the column `email` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
-  - Made the column `name_of_firm` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
-  - Made the column `solicitor_acting` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
-  - Made the column `telephone` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
-
-*/
--- DropForeignKey
-ALTER TABLE "solicitors" DROP CONSTRAINT "solicitors_address_country_lid_fkey";
-
--- AlterTable
-ALTER TABLE "solicitors" ALTER COLUMN "address_country_lid" SET NOT NULL,
-ALTER COLUMN "address_line1" SET NOT NULL,
-ALTER COLUMN "address_post_code" SET NOT NULL,
-ALTER COLUMN "email" SET NOT NULL,
-ALTER COLUMN "name_of_firm" SET NOT NULL,
-ALTER COLUMN "solicitor_acting" SET NOT NULL,
-DROP COLUMN "sort_code",
-ADD COLUMN     "sort_code" INTEGER,
-ALTER COLUMN "telephone" SET NOT NULL;
-
--- AddForeignKey
-ALTER TABLE "solicitors" ADD CONSTRAINT "solicitors_address_country_lid_fkey" FOREIGN KEY ("address_country_lid") REFERENCES "lookups"("id") ON DELETE RESTRICT ON UPDATE CASCADE;
+/*
+  Warnings:
+
+  - The `sort_code` column on the `solicitors` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - Made the column `address_country_lid` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
+  - Made the column `address_line1` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
+  - Made the column `address_post_code` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
+  - Made the column `email` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
+  - Made the column `name_of_firm` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
+  - Made the column `solicitor_acting` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
+  - Made the column `telephone` on table `solicitors` required. This step will fail if there are existing NULL values in that column.
+
+*/
+-- DropForeignKey
+ALTER TABLE "solicitors" DROP CONSTRAINT "solicitors_address_country_lid_fkey";
+
+-- AlterTable
+ALTER TABLE "solicitors" ALTER COLUMN "address_country_lid" SET NOT NULL,
+ALTER COLUMN "address_line1" SET NOT NULL,
+ALTER COLUMN "address_post_code" SET NOT NULL,
+ALTER COLUMN "email" SET NOT NULL,
+ALTER COLUMN "name_of_firm" SET NOT NULL,
+ALTER COLUMN "solicitor_acting" SET NOT NULL,
+DROP COLUMN "sort_code",
+ADD COLUMN     "sort_code" INTEGER,
+ALTER COLUMN "telephone" SET NOT NULL;
+
+-- AddForeignKey
+ALTER TABLE "solicitors" ADD CONSTRAINT "solicitors_address_country_lid_fkey" FOREIGN KEY ("address_country_lid") REFERENCES "lookups"("id") ON DELETE RESTRICT ON UPDATE CASCADE;

package/prisma/migrations/20250506054831_update_note_schema/migration.sql

@@ -1,12 +1,12 @@
-/*
-  Warnings:
-
-  - A unique constraint covering the columns `[application_id]` on the table `application_notes` will be added. If there are existing duplicate values, this will fail.
-  - A unique constraint covering the columns `[application_id]` on the table `brokers` will be added. If there are existing duplicate values, this will fail.
-
-*/
--- CreateIndex
-CREATE UNIQUE INDEX "application_notes_application_id_key" ON "application_notes"("application_id");
-
--- CreateIndex
-CREATE UNIQUE INDEX "brokers_application_id_key" ON "brokers"("application_id");
+/*
+  Warnings:
+
+  - A unique constraint covering the columns `[application_id]` on the table `application_notes` will be added. If there are existing duplicate values, this will fail.
+  - A unique constraint covering the columns `[application_id]` on the table `brokers` will be added. If there are existing duplicate values, this will fail.
+
+*/
+-- CreateIndex
+CREATE UNIQUE INDEX "application_notes_application_id_key" ON "application_notes"("application_id");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "brokers_application_id_key" ON "brokers"("application_id");

package/prisma/migrations/20250506142218_update_broker_schema/migration.sql

@@ -1,17 +1,17 @@
-/*
-  Warnings:
-
-  - You are about to drop the column `application_id` on the `brokers` table. All the data in the column will be lost.
-  - A unique constraint covering the columns `[broker_id]` on the table `brokers` will be added. If there are existing duplicate values, this will fail.
-  - Made the column `broker_id` on table `brokers` required. This step will fail if there are existing NULL values in that column.
-
-*/
--- DropIndex
-DROP INDEX "brokers_application_id_key";
-
--- AlterTable
-ALTER TABLE "brokers" DROP COLUMN "application_id",
-ALTER COLUMN "broker_id" SET NOT NULL;
-
--- CreateIndex
-CREATE UNIQUE INDEX "brokers_broker_id_key" ON "brokers"("broker_id");
+/*
+  Warnings:
+
+  - You are about to drop the column `application_id` on the `brokers` table. All the data in the column will be lost.
+  - A unique constraint covering the columns `[broker_id]` on the table `brokers` will be added. If there are existing duplicate values, this will fail.
+  - Made the column `broker_id` on table `brokers` required. This step will fail if there are existing NULL values in that column.
+
+*/
+-- DropIndex
+DROP INDEX "brokers_application_id_key";
+
+-- AlterTable
+ALTER TABLE "brokers" DROP COLUMN "application_id",
+ALTER COLUMN "broker_id" SET NOT NULL;
+
+-- CreateIndex
+CREATE UNIQUE INDEX "brokers_broker_id_key" ON "brokers"("broker_id");

package/prisma/migrations/20250506190258_update_application_note_schema/migration.sql

@@ -1,32 +1,32 @@
-/*
-  Warnings:
-
-  - You are about to drop the column `comment` on the `application_notes` table. All the data in the column will be lost.
-  - The `created_by` column on the `application_notes` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - The `auto_created` column on the `application_notes` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - The `assigned_by` column on the `application_notes` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - The `reminder_status` column on the `application_notes` table would be dropped and recreated. This will lead to data loss if there is data in the column.
-  - A unique constraint covering the columns `[note_id]` on the table `application_notes` will be added. If there are existing duplicate values, this will fail.
-  - Made the column `note_id` on table `application_notes` required. This step will fail if there are existing NULL values in that column.
-
-*/
--- DropIndex
-DROP INDEX "application_notes_application_id_key";
-
--- AlterTable
-ALTER TABLE "application_notes" DROP COLUMN "comment",
-ADD COLUMN     "comments" JSONB,
-ADD COLUMN     "pretty_created_on" TEXT,
-ALTER COLUMN "note_id" SET NOT NULL,
-DROP COLUMN "created_by",
-ADD COLUMN     "created_by" INTEGER,
-DROP COLUMN "auto_created",
-ADD COLUMN     "auto_created" BOOLEAN NOT NULL DEFAULT false,
-ALTER COLUMN "additional_data" SET DATA TYPE TEXT,
-DROP COLUMN "assigned_by",
-ADD COLUMN     "assigned_by" INTEGER,
-DROP COLUMN "reminder_status",
-ADD COLUMN     "reminder_status" INTEGER NOT NULL DEFAULT 0;
-
--- CreateIndex
-CREATE UNIQUE INDEX "application_notes_note_id_key" ON "application_notes"("note_id");
+/*
+  Warnings:
+
+  - You are about to drop the column `comment` on the `application_notes` table. All the data in the column will be lost.
+  - The `created_by` column on the `application_notes` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - The `auto_created` column on the `application_notes` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - The `assigned_by` column on the `application_notes` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - The `reminder_status` column on the `application_notes` table would be dropped and recreated. This will lead to data loss if there is data in the column.
+  - A unique constraint covering the columns `[note_id]` on the table `application_notes` will be added. If there are existing duplicate values, this will fail.
+  - Made the column `note_id` on table `application_notes` required. This step will fail if there are existing NULL values in that column.
+
+*/
+-- DropIndex
+DROP INDEX "application_notes_application_id_key";
+
+-- AlterTable
+ALTER TABLE "application_notes" DROP COLUMN "comment",
+ADD COLUMN     "comments" JSONB,
+ADD COLUMN     "pretty_created_on" TEXT,
+ALTER COLUMN "note_id" SET NOT NULL,
+DROP COLUMN "created_by",
+ADD COLUMN     "created_by" INTEGER,
+DROP COLUMN "auto_created",
+ADD COLUMN     "auto_created" BOOLEAN NOT NULL DEFAULT false,
+ALTER COLUMN "additional_data" SET DATA TYPE TEXT,
+DROP COLUMN "assigned_by",
+ADD COLUMN     "assigned_by" INTEGER,
+DROP COLUMN "reminder_status",
+ADD COLUMN     "reminder_status" INTEGER NOT NULL DEFAULT 0;
+
+-- CreateIndex
+CREATE UNIQUE INDEX "application_notes_note_id_key" ON "application_notes"("note_id");