procbay-schema 1.0.13 → 1.0.15

package/README.md

@@ -1,8 +1,8 @@
-# procbay-schema
+# p2p-schema
 
 A set of utilities for managing Prisma database schemas, seeding, and maintenance operations for the Procure-to-Pay system.
 
-[![npm version](https://img.shields.io/npm/v/procbay-schema.svg)](https://www.npmjs.com/package/procbay-schema)
+[![npm version](https://img.shields.io/npm/v/p2p-schema.svg)](https://www.npmjs.com/package/p2p-schema)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
 ## Features
@@ -18,7 +18,7 @@ A set of utilities for managing Prisma database schemas, seeding, and maintenanc
 ## Installation
 
 ```bash
-npm install procbay-schema
+npm install p2p-schema
 ```
 
 ## Using Prisma Client
@@ -26,7 +26,7 @@ npm install procbay-schema
 This package includes the full Prisma client generated from the schema, making it easy to use in your projects:
 
 ```javascript
-import { PrismaClient } from "procbay-schema";
+import { PrismaClient } from "p2p-schema";
 
 // Create a new Prisma client instance
 const prisma = new PrismaClient();
@@ -127,7 +127,7 @@ npx prisma-truncate --db YOUR_DB_NAME --tables users,posts --dry-run
 You can also use the package programmatically:
 
 ```javascript
-import { syncDatabase, seedDatabase, truncateTables } from "procbay-schema";
+import { syncDatabase, seedDatabase, truncateTables } from "p2p-schema";
 
 // Sync schemas
 syncDatabase({ db: "YOUR_DB_NAME" });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "procbay-schema",
-  "version": "1.0.13",
+  "version": "1.0.15",
   "description": "A set of utilities for managing Prisma database schemas, seeding, and maintenance operations for the Procure-to-Pay system",
   "main": "src/prisma/index.js",
   "type": "module",

package/prisma/.env

@@ -4,6 +4,10 @@
 # Prisma supports the native connection string format for PostgreSQL, MySQL, SQLite, SQL Server, MongoDB and CockroachDB.
 # See the documentation for all the connection string options: https://pris.ly/d/connection-strings
 
-DEFAULT_DATABASE_URL="postgresql://postgres:root@localhost:5432/procbay_new_db?schema=procbay_schema"
+DEFAULT_DATABASE_URL="postgresql://postgres:root@localhost:5432/procbay_db?schema=procbay_schema"
+ARVIND_DATABASE_URL="postgresql://p2puser:dShd190AK0e@172.16.2.27:5432/arvind_procbay_db?schema=procbay_schema"
+AZHAR_DATABASE_URL="postgresql://p2puser:dShd190AK0e@172.16.2.27:5432/azhar_procbay_db?schema=procbay_schema"
+HARSH_DATABASE_URL="postgresql://p2puser:dShd190AK0e@172.16.2.27:5432/harsh_procbay_db?schema=procbay_schema"
+VAIBHAV_DATABASE_URL="postgresql://p2puser:dShd190AK0e@172.16.2.27:5432/vaibhav_procbay_db?schema=procbay_schema"
 DETAILED_LOGGING=true
 LOG_LEVEL=info

package/prisma/migrations/{20250729100954_ → 20250728105546_}/migration.sql

@@ -7,9 +7,6 @@
   - A unique constraint covering the columns `[department_budget_id,category_id]` on the table `category_budgets` will be added. If there are existing duplicate values, this will fail.
 
 */
--- AlterEnum
-ALTER TYPE "AlertTypeEnum" ADD VALUE 'EXPORT';
-
 -- DropForeignKey
 ALTER TABLE "category_budgets" DROP CONSTRAINT "category_budgets_budget_id_fkey";
 

package/prisma/migrations/20250729100247_alter_admin_alert_enum/migration.sql

@@ -0,0 +1,5 @@
+-- AlterEnum
+ALTER TYPE "AlertTypeEnum" ADD VALUE 'EXPORT';
+
+-- AlterTable
+ALTER TABLE "export_logs" ALTER COLUMN "expires_at" SET DEFAULT NOW() + INTERVAL '7 days';

package/prisma/migrations/20250730101549_added_code_in_budget_table/migration.sql

@@ -0,0 +1,18 @@
+/*
+  Warnings:
+
+  - A unique constraint covering the columns `[code]` on the table `budgets` will be added. If there are existing duplicate values, this will fail.
+  - A unique constraint covering the columns `[code,fiscal_year]` on the table `budgets` will be added. If there are existing duplicate values, this will fail.
+
+*/
+-- AlterTable
+ALTER TABLE "budgets" ADD COLUMN     "code" TEXT;
+
+-- AlterTable
+ALTER TABLE "export_logs" ALTER COLUMN "expires_at" SET DEFAULT NOW() + INTERVAL '7 days';
+
+-- CreateIndex
+CREATE UNIQUE INDEX "budgets_code_key" ON "budgets"("code");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "budgets_code_fiscal_year_key" ON "budgets"("code", "fiscal_year");

package/prisma/migrations/20250731061624_alter_expense_table/migration.sql

@@ -0,0 +1,16 @@
+/*
+  Warnings:
+
+  - You are about to drop the column `createdAt` on the `expenses` table. All the data in the column will be lost.
+  - You are about to drop the column `updatedAt` on the `expenses` table. All the data in the column will be lost.
+  - Added the required column `updated_at` to the `expenses` table without a default value. This is not possible if the table is not empty.
+
+*/
+-- AlterTable
+ALTER TABLE "expenses" DROP COLUMN "createdAt",
+DROP COLUMN "updatedAt",
+ADD COLUMN     "created_at" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+ADD COLUMN     "updated_at" TIMESTAMP(3) NOT NULL;
+
+-- AlterTable
+ALTER TABLE "export_logs" ALTER COLUMN "expires_at" SET DEFAULT NOW() + INTERVAL '7 days';

package/prisma/migrations/{20250729122741_alter_vendor_refrence_table → 20250731072247_alter_catgeory_budget_table}/migration.sql

@@ -1,5 +1,5 @@
 -- AlterTable
-ALTER TABLE "export_logs" ALTER COLUMN "expires_at" SET DEFAULT NOW() + INTERVAL '7 days';
+ALTER TABLE "category_budgets" ADD COLUMN     "fiscal_year" TEXT;
 
 -- AlterTable
-ALTER TABLE "vendor_references" ADD COLUMN     "meta_data" JSONB;
+ALTER TABLE "export_logs" ALTER COLUMN "expires_at" SET DEFAULT NOW() + INTERVAL '7 days';

package/prisma/migrations/{20250806125844_init_fast_catalogue_tables → 20250806123912_init_fast_catalogue_tables}/migration.sql

@@ -95,3 +95,6 @@ ALTER TABLE "requested_catalogue_items" ADD CONSTRAINT "requested_catalogue_item
 
 -- AddForeignKey
 ALTER TABLE "requested_catalogue_vendors" ADD CONSTRAINT "requested_catalogue_vendors_req_catalogue_id_fkey" FOREIGN KEY ("req_catalogue_id") REFERENCES "requested_catalogues"("id") ON DELETE CASCADE ON UPDATE CASCADE;
+
+-- AddForeignKey
+ALTER TABLE "requested_catalogue_vendors" ADD CONSTRAINT "requested_catalogue_vendors_vendor_id_fkey" FOREIGN KEY ("vendor_id") REFERENCES "vendors"("id") ON DELETE CASCADE ON UPDATE CASCADE;

package/prisma/migrations/20250811094537_added_purchase_intake_status_enum/migration.sql

@@ -0,0 +1,18 @@
+-- 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 "PurchaseIntakeStatusEnum" ADD VALUE 'APPROVED';
+ALTER TYPE "PurchaseIntakeStatusEnum" ADD VALUE 'IN_PROGRESS';
+ALTER TYPE "PurchaseIntakeStatusEnum" ADD VALUE 'PENDING';
+ALTER TYPE "PurchaseIntakeStatusEnum" ADD VALUE 'REJECTED';
+ALTER TYPE "PurchaseIntakeStatusEnum" ADD VALUE 'COMPLETED';
+ALTER TYPE "PurchaseIntakeStatusEnum" ADD VALUE 'CANCELLED';
+ALTER TYPE "PurchaseIntakeStatusEnum" ADD VALUE 'AUTO_APPROVED';
+
+-- AlterTable
+ALTER TABLE "export_logs" ALTER COLUMN "expires_at" SET DEFAULT NOW() + INTERVAL '7 days';

package/prisma/migrations/20250811094955_alter_pise/migration.sql

@@ -0,0 +1,5 @@
+-- AlterTable
+ALTER TABLE "export_logs" ALTER COLUMN "expires_at" SET DEFAULT NOW() + INTERVAL '7 days';
+
+-- AlterTable
+ALTER TABLE "purchase_intakes" ALTER COLUMN "status" SET DEFAULT 'PENDING';

package/prisma/migrations/{20250811095409_ → 20250811104547_}/migration.sql

@@ -17,6 +17,3 @@ COMMIT;
 
 -- AlterTable
 ALTER TABLE "export_logs" ALTER COLUMN "expires_at" SET DEFAULT NOW() + INTERVAL '7 days';
-
--- AlterTable
-ALTER TABLE "purchase_intakes" ALTER COLUMN "status" SET DEFAULT 'PENDING';