@optimatech88/titomeet-shared-lib 1.0.35 → 1.0.36

package/prisma/migrations/20250604105002_added_category_children/migration.sql

@@ -1,31 +0,0 @@
-/*
-  Warnings:
-
-  - You are about to drop the column `interests` on the `UserInterests` table. All the data in the column will be lost.
-
-*/
--- AlterTable
-ALTER TABLE "EventCategory" ADD COLUMN     "parentId" TEXT;
-
--- AlterTable
-ALTER TABLE "UserInterests" DROP COLUMN "interests";
-
--- CreateTable
-CREATE TABLE "_EventCategoryToUserInterests" (
-    "A" TEXT NOT NULL,
-    "B" TEXT NOT NULL,
-
-    CONSTRAINT "_EventCategoryToUserInterests_AB_pkey" PRIMARY KEY ("A","B")
-);
-
--- CreateIndex
-CREATE INDEX "_EventCategoryToUserInterests_B_index" ON "_EventCategoryToUserInterests"("B");
-
--- AddForeignKey
-ALTER TABLE "EventCategory" ADD CONSTRAINT "EventCategory_parentId_fkey" FOREIGN KEY ("parentId") REFERENCES "EventCategory"("id") ON DELETE SET NULL ON UPDATE CASCADE;
-
--- AddForeignKey
-ALTER TABLE "_EventCategoryToUserInterests" ADD CONSTRAINT "_EventCategoryToUserInterests_A_fkey" FOREIGN KEY ("A") REFERENCES "EventCategory"("id") ON DELETE CASCADE ON UPDATE CASCADE;
-
--- AddForeignKey
-ALTER TABLE "_EventCategoryToUserInterests" ADD CONSTRAINT "_EventCategoryToUserInterests_B_fkey" FOREIGN KEY ("B") REFERENCES "UserInterests"("id") ON DELETE CASCADE ON UPDATE CASCADE;

package/prisma/migrations/20250611180441_added_chat_files/migration.sql

@@ -1,11 +0,0 @@
-/*
-  Warnings:
-
-  - You are about to drop the column `mediaType` on the `Message` table. All the data in the column will be lost.
-  - You are about to drop the column `mediaUrl` on the `Message` table. All the data in the column will be lost.
-
-*/
--- AlterTable
-ALTER TABLE "Message" DROP COLUMN "mediaType",
-DROP COLUMN "mediaUrl",
-ADD COLUMN     "files" JSONB;

package/prisma/migrations/20250617111807_updated_notification_type/migration.sql

@@ -1,13 +0,0 @@
--- AlterEnum
--- This migration adds more than one value to an enum.
--- With PostgreSQL versions 11 and earlier, this is not possible
--- in a single migration. This can be worked around by creating
--- multiple migrations, each migration adding only one value to
--- the enum.
-
-
-ALTER TYPE "NotificationType" ADD VALUE 'EVENT_VALIDATION';
-ALTER TYPE "NotificationType" ADD VALUE 'EVENT_REJECTION';
-ALTER TYPE "NotificationType" ADD VALUE 'EVENT_ASSIGNMENT';
-ALTER TYPE "NotificationType" ADD VALUE 'EVENT_ASSIGNMENT_APPROVAL';
-ALTER TYPE "NotificationType" ADD VALUE 'EVENT_ASSIGNMENT_REJECTION';

package/prisma/migrations/20250716081532_added_newslettter/migration.sql

@@ -1,13 +0,0 @@
--- CreateTable
-CREATE TABLE "Newsletter" (
-    "id" TEXT NOT NULL,
-    "email" TEXT NOT NULL,
-    "unsubscribedAt" TIMESTAMP(3),
-    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
-    "updatedAt" TIMESTAMP(3) NOT NULL,
-
-    CONSTRAINT "Newsletter_pkey" PRIMARY KEY ("id")
-);
-
--- CreateIndex
-CREATE UNIQUE INDEX "Newsletter_email_key" ON "Newsletter"("email");

package/prisma/migrations/migration_lock.toml

@@ -1,3 +0,0 @@
-# Please do not edit this file manually
-# It should be added in your version-control system (e.g., Git)
-provider = "postgresql"