Blitz
Explore posts from serversDTDrizzle Team
•Created by Blitz on 11/24/2024 in #help
Why does drizzle want to request the same column twice from db?
Why is that happening?
5 replies
DTDrizzle Team
•Created by Blitz on 11/24/2024 in #help
Why does drizzle want to request the same column twice from db?
Query: select "sessions"."id", "sessions"."token", "sessions"."refresh_token", "sessions"."rejected_at", "sessions"."created_at", json_build_object('id',"users"."id",'username',"users"."username",'discordUsername',"users"."discord_username",'discordId',"users"."discord_id",'createdAt',"users"."created_at",'email',"users"."email"), coalesce(
json_agg(json_build_object('id',"sq"."id",'issuedTo',"sq"."issued_to",'issuedUntil',"sq"."issued_at",'issuedBy',"sq"."issued_by",'reason',"sq"."reason",'issuedAt',"sq"."issued_at")
)
FILTER (WHERE "sq"."id" IS NOT NULL AND "sq"."issued_to" IS NOT NULL AND "sq"."issued_at" IS NOT NULL AND "sq"."issued_by" IS NOT NULL AND "sq"."reason" IS NOT NULL AND "sq"."issued_at" IS NOT NULL)
,'[]') from "sessions" left join "users" on "sessions"."user_id" = "users"."id" left join (select "id", "issued_at", "issued_at", "issued_by", "issued_to", "reason" from "bans" where "bans"."issued_at" > $1) "sq" on "users"."id" = "sq"."issued_to" where "sessions"."token" = $2 group by "users"."id", "sessions"."id"
Query: select "sessions"."id", "sessions"."token", "sessions"."refresh_token", "sessions"."rejected_at", "sessions"."created_at", json_build_object('id',"users"."id",'username',"users"."username",'discordUsername',"users"."discord_username",'discordId',"users"."discord_id",'createdAt',"users"."created_at",'email',"users"."email"), coalesce(
json_agg(json_build_object('id',"sq"."id",'issuedTo',"sq"."issued_to",'issuedUntil',"sq"."issued_at",'issuedBy',"sq"."issued_by",'reason',"sq"."reason",'issuedAt',"sq"."issued_at")
)
FILTER (WHERE "sq"."id" IS NOT NULL AND "sq"."issued_to" IS NOT NULL AND "sq"."issued_at" IS NOT NULL AND "sq"."issued_by" IS NOT NULL AND "sq"."reason" IS NOT NULL AND "sq"."issued_at" IS NOT NULL)
,'[]') from "sessions" left join "users" on "sessions"."user_id" = "users"."id" left join (select "id", "issued_at", "issued_at", "issued_by", "issued_to", "reason" from "bans" where "bans"."issued_at" > $1) "sq" on "users"."id" = "sq"."issued_to" where "sessions"."token" = $2 group by "users"."id", "sessions"."id"
5 replies
DTDrizzle Team
•Created by Blitz on 1/8/2024 in #help
Migrations problem
found out that the problem was update statement on updatedAt, but now i don't know how to best perform updatedAt field so that it's working automatically
3 replies
DTDrizzle Team
•Created by Blitz on 1/8/2024 in #help
Migrations problem
and lastly my current migration file
CREATE TABLE IF NOT EXISTS "children" (
"cuid" serial PRIMARY KEY NOT NULL,
"createdAt" timestamp DEFAULT now(),
"updatedAt" timestamp DEFAULT CURRENT_TIMESTAMP(3) on update CURRENT_TIMESTAMP(3),
"name" varchar(100) NOT NULL,
"surname" varchar(100) NOT NULL,
"pesel" integer,
"birthDate" date NOT NULL,
"address" text,
"allergies" json,
CONSTRAINT "children_pesel_unique" UNIQUE("pesel")
);
--> statement-breakpoint
CREATE TABLE IF NOT EXISTS "parentToChild" (
"parentId" serial NOT NULL,
"childId" serial NOT NULL
);
--> statement-breakpoint
CREATE TABLE IF NOT EXISTS "users" (
"cuid" serial PRIMARY KEY NOT NULL,
"createdAt" timestamp DEFAULT now(),
"updatedAt" timestamp DEFAULT CURRENT_TIMESTAMP(3) on update CURRENT_TIMESTAMP(3),
"name" varchar(100) NOT NULL,
"surname" varchar(100) NOT NULL,
"pesel" integer,
"address" text,
"personalIdentification" varchar,
"password" varchar NOT NULL,
"email" varchar NOT NULL,
"isActive" boolean DEFAULT true NOT NULL,
CONSTRAINT "users_pesel_unique" UNIQUE("pesel"),
CONSTRAINT "users_personalIdentification_unique" UNIQUE("personalIdentification"),
CONSTRAINT "users_email_unique" UNIQUE("email")
);
--> statement-breakpoint
DO $$ BEGIN
ALTER TABLE "parentToChild" ADD CONSTRAINT "parentToChild_parentId_users_cuid_fk" FOREIGN KEY ("parentId") REFERENCES "public"."users"("cuid") ON DELETE no action ON UPDATE no action;
EXCEPTION
WHEN duplicate_object THEN null;
END $$;
--> statement-breakpoint
DO $$ BEGIN
ALTER TABLE "parentToChild" ADD CONSTRAINT "parentToChild_childId_children_cuid_fk" FOREIGN KEY ("childId") REFERENCES "public"."children"("cuid") ON DELETE no action ON UPDATE no action;
EXCEPTION
WHEN duplicate_object THEN null;
END $$;
CREATE TABLE IF NOT EXISTS "children" (
"cuid" serial PRIMARY KEY NOT NULL,
"createdAt" timestamp DEFAULT now(),
"updatedAt" timestamp DEFAULT CURRENT_TIMESTAMP(3) on update CURRENT_TIMESTAMP(3),
"name" varchar(100) NOT NULL,
"surname" varchar(100) NOT NULL,
"pesel" integer,
"birthDate" date NOT NULL,
"address" text,
"allergies" json,
CONSTRAINT "children_pesel_unique" UNIQUE("pesel")
);
--> statement-breakpoint
CREATE TABLE IF NOT EXISTS "parentToChild" (
"parentId" serial NOT NULL,
"childId" serial NOT NULL
);
--> statement-breakpoint
CREATE TABLE IF NOT EXISTS "users" (
"cuid" serial PRIMARY KEY NOT NULL,
"createdAt" timestamp DEFAULT now(),
"updatedAt" timestamp DEFAULT CURRENT_TIMESTAMP(3) on update CURRENT_TIMESTAMP(3),
"name" varchar(100) NOT NULL,
"surname" varchar(100) NOT NULL,
"pesel" integer,
"address" text,
"personalIdentification" varchar,
"password" varchar NOT NULL,
"email" varchar NOT NULL,
"isActive" boolean DEFAULT true NOT NULL,
CONSTRAINT "users_pesel_unique" UNIQUE("pesel"),
CONSTRAINT "users_personalIdentification_unique" UNIQUE("personalIdentification"),
CONSTRAINT "users_email_unique" UNIQUE("email")
);
--> statement-breakpoint
DO $$ BEGIN
ALTER TABLE "parentToChild" ADD CONSTRAINT "parentToChild_parentId_users_cuid_fk" FOREIGN KEY ("parentId") REFERENCES "public"."users"("cuid") ON DELETE no action ON UPDATE no action;
EXCEPTION
WHEN duplicate_object THEN null;
END $$;
--> statement-breakpoint
DO $$ BEGIN
ALTER TABLE "parentToChild" ADD CONSTRAINT "parentToChild_childId_children_cuid_fk" FOREIGN KEY ("childId") REFERENCES "public"."children"("cuid") ON DELETE no action ON UPDATE no action;
EXCEPTION
WHEN duplicate_object THEN null;
END $$;
3 replies