adding avatar to database schema and fixing cascading between file an…

…d user models

backend/prisma/migrations/20231212081228_avatar_file_in_user_model/migration.sql

@@ -0,0 +1,8 @@
+/*
+  Warnings:
+
+  - A unique constraint covering the columns `[uploadedById]` on the table `File` will be added. If there are existing duplicate values, this will fail.
+
+*/
+-- CreateIndex
+CREATE UNIQUE INDEX "File_uploadedById_key" ON "File"("uploadedById");

backend/prisma/migrations/20231215040248_adding_cascade_to_file_and_user_relation/migration.sql

@@ -0,0 +1,5 @@
+-- DropForeignKey
+ALTER TABLE "File" DROP CONSTRAINT "File_uploadedById_fkey";
+
+-- AddForeignKey
+ALTER TABLE "File" ADD CONSTRAINT "File_uploadedById_fkey" FOREIGN KEY ("uploadedById") REFERENCES "User"("id") ON DELETE CASCADE ON UPDATE CASCADE;

backend/prisma/schema.prisma

@@ -33,7 +33,7 @@ model User {
     Block2         Block[]             @relation("Block2")
     PendingFriend1 PendingFriendship[] @relation("PendingFriend1")
     PendingFriend2 PendingFriendship[] @relation("PendingFriend2")
-    files          File[]
+    avatar         File?
     sockets        UserSockets[]
 }
 
@@ -104,9 +104,9 @@ model File {
     url          String
     mimeType     String
     fileSize     Int
-    uploadedById Int
+    uploadedById Int      @unique
     createdAt    DateTime @default(now())
     updatedAt    DateTime @updatedAt
 
-    uploadedBy User @relation(fields: [uploadedById], references: [id])
+    uploadedBy User @relation(fields: [uploadedById], references: [id], onDelete: Cascade)
 }