Use BISERIAL instead of SERIAL in migration

dust-tt · Jan 31, 2025 · b94458d · b94458d
1 parent e5ea24d
commit b94458d
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/front/migrations/db/migration_162.sql b/front/migrations/db/migration_162.sql
@@ -1,6 +1,6 @@
 -- Migration created on Jan 27, 2025
 CREATE TABLE IF NOT EXISTS "agent_reasoning_configurations" (
-    "id" SERIAL,
+    "id" BIGSERIAL,
     "createdAt" TIMESTAMP WITH TIME ZONE NOT NULL,
     "updatedAt" TIMESTAMP WITH TIME ZONE NOT NULL,
     "sId" VARCHAR(255) NOT NULL,
@@ -20,7 +20,7 @@ CREATE INDEX CONCURRENTLY "agent_reasoning_configurations_agent_configuration_id
 CREATE INDEX CONCURRENTLY "agent_reasoning_configurations_workspace_id" ON "agent_reasoning_configurations" ("workspaceId");
 
 CREATE TABLE IF NOT EXISTS "agent_reasoning_actions" (
-    "id" SERIAL,
+    "id" BIGSERIAL,
     "createdAt" TIMESTAMP WITH TIME ZONE NOT NULL,
     "updatedAt" TIMESTAMP WITH TIME ZONE NOT NULL,
     "runId" VARCHAR(255),