From c872961eb19e7d12806827ce5cd7de14bdd42929 Mon Sep 17 00:00:00 2001
From: dhanabalan <digitalmanufacturingiiot@gmail.com>
Date: Thu, 10 Sep 2026 17:50:28 +0530
Subject: [PATCH] Added status column in production order table

---
 ...rint_panel_status_to_production_orders.php | 36 +++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 database/migrations/2026_05_07_112900_add_print_status_and_print_panel_status_to_production_orders.php

diff --git a/database/migrations/2026_05_07_112900_add_print_status_and_print_panel_status_to_production_orders.php b/database/migrations/2026_05_07_112900_add_print_status_and_print_panel_status_to_production_orders.php
new file mode 100644
index 0000000..49471d2
--- /dev/null
+++ b/database/migrations/2026_05_07_112900_add_print_status_and_print_panel_status_to_production_orders.php
@@ -0,0 +1,36 @@
+<?php
+
+use Illuminate\Database\Migrations\Migration;
+
+return new class extends Migration
+{
+    /**
+     * Run the migrations.
+     */
+    public function up(): void
+    {
+        $sql1 = <<<'SQL'
+        ALTER TABLE production_orders
+        ADD COLUMN print_status TEXT DEFAULT NULL
+        SQL;
+
+        DB::statement($sql1);
+
+        $sql2 = <<<'SQL'
+        ALTER TABLE production_orders
+        ADD COLUMN print_panel_status TEXT DEFAULT NULL
+        SQL;
+
+        DB::statement($sql2);
+    }
+
+    /**
+     * Reverse the migrations.
+     */
+    public function down(): void
+    {
+        // Schema::table('production_orders', function (Blueprint $table) {
+        //     //
+        // });
+    }
+};