zendev Comments - Answer Overflow

I hadn’t changed any names or anything in the schema except for adding that column which you can see at the bottom of the migration file I shared above.

21 replies

DTDrizzle Team

•Created by Dr. Pure on 7/14/2024 in #help

Issue with constraint primary key when using drizzle-kit push 2 times.

It was a project with existing migration files, yes. Before upgrade I was on drizzle-kit 0.19, now on 0.23

21 replies

DTDrizzle Team

•Created by Dr. Pure on 7/14/2024 in #help

Issue with constraint primary key when using drizzle-kit push 2 times.

Btw this just happened to me after updating to the latest version of drizzle-orm and drizzle-kit

21 replies

DTDrizzle Team

•Created by Dr. Pure on 7/14/2024 in #help

Issue with constraint primary key when using drizzle-kit push 2 times.

I am running into a similar issue with migrate. The migration file looks like this

ALTER TABLE "artists_to_songs" DROP CONSTRAINT "artists_to_songs_artist_id_song_id";--> statement-breakpoint
ALTER TABLE "users_to_scenes" DROP CONSTRAINT "users_to_scenes_user_id_scene_unique_name";--> statement-breakpoint
ALTER TABLE "artists_to_songs" ADD CONSTRAINT "artists_to_songs_artist_id_song_id_pk" PRIMARY KEY("artist_id","song_id");--> statement-breakpoint
ALTER TABLE "users_to_scenes" ADD CONSTRAINT "users_to_scenes_user_id_scene_unique_name_pk" PRIMARY KEY("user_id","scene_unique_name");--> statement-breakpoint
ALTER TABLE "songs" ADD COLUMN "image_colors" text[] NOT NULL;

ALTER TABLE "artists_to_songs" DROP CONSTRAINT "artists_to_songs_artist_id_song_id";--> statement-breakpoint
ALTER TABLE "users_to_scenes" DROP CONSTRAINT "users_to_scenes_user_id_scene_unique_name";--> statement-breakpoint
ALTER TABLE "artists_to_songs" ADD CONSTRAINT "artists_to_songs_artist_id_song_id_pk" PRIMARY KEY("artist_id","song_id");--> statement-breakpoint
ALTER TABLE "users_to_scenes" ADD CONSTRAINT "users_to_scenes_user_id_scene_unique_name_pk" PRIMARY KEY("user_id","scene_unique_name");--> statement-breakpoint
ALTER TABLE "songs" ADD COLUMN "image_colors" text[] NOT NULL;

So you can see that drizzle-kit is dropping all composite PKs and then readding? It produces the following error when running drizzle-kit migrate:

PostgresError: constraint "users_to_scenes_user_id_scene_unique_name" of relation "users_to_scenes" does not exist

PostgresError: constraint "users_to_scenes_user_id_scene_unique_name" of relation "users_to_scenes" does not exist

21 replies

DTDrizzle Team

•Created by Ilan Yehezkely on 3/19/2024 in #help

Neon postgres, drop all fk constraints on every push without any changes

I have the same issue, did you ever figure out why this was happening?

3 replies

DTDrizzle Team

•Created by web_dev_dk on 7/3/2024 in #help

Keep getting relation constraint error when migrating

Without having to drop all the migrations preferably lol

5 replies

DTDrizzle Team

•Created by web_dev_dk on 7/3/2024 in #help

Keep getting relation constraint error when migrating

Did you manage to resolve this or figure out what was going wrong?

5 replies

DTDrizzle Team

•Created by web_dev_dk on 7/3/2024 in #help

Keep getting relation constraint error when migrating

I am running into almost the identical issue

5 replies

TTCTheo's Typesafe Cult

•Created by West side ⁉ on 10/14/2023 in #questions

Drizzle-ORM+PSQL: sorry, too many clients already

The solution George sent above looks good, you basically just create a singleton to use for dev instances and leave it as is for production instances

9 replies

CDCloudflare Developers

•Created by Idle on 11/10/2023 in #general-help

CORS/Origin issues

Hi, unsure if this is the same issue but I'm getting this error in my console: Access to audio at 'https://songs.songbyrd.world/65c85152-81a5-43a4-9fd1-db476ce97b6a.mpeg' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. songs.songbyrd.world/65c85152-81a5-43a4-9fd1-db476ce97b6a.mpeg:1 GET https://songs.songbyrd.world/65c85152-81a5-43a4-9fd1-db476ce97b6a.mpeg net::ERR_FAILED My CORS policy on the bucket is like this: [ { "AllowedOrigins": [ "http://localhost:3000" ], "AllowedMethods": [ "GET", "PUT" ], "AllowedHeaders": [ "Content-Type" ] } ] Can anyone point me in the right direction?

18 replies

TTCTheo's Typesafe Cult

•Created by tsuki on 11/2/2023 in #questions

onSuccess, onError and onSettled deprecated next major version?

Perfect thanks mate

16 replies

TTCTheo's Typesafe Cult

•Created by tsuki on 11/2/2023 in #questions

onSuccess, onError and onSettled deprecated next major version?

Yeah this is what I wanted to do but can’t find the queryClient config in the t3 setup

16 replies

TTCTheo's Typesafe Cult

•Created by tsuki on 11/2/2023 in #questions

onSuccess, onError and onSettled deprecated next major version?

I could very well be wrong but could someone enlighten me on how to do useQuery error handling w trpc?

16 replies

TTCTheo's Typesafe Cult

•Created by tsuki on 11/2/2023 in #questions

onSuccess, onError and onSettled deprecated next major version?

Hi just read through the article, everything makes sense but in the t3 setup there isn’t a way to do what they did regarding toasting an error, bc the onError callback from trpc occurs on the server side, inside the pages/api folder?

16 replies

Gaming

Programming