Kajetan Szymczak

> > Tried this locally, but unfortunately, it crashed my app. Are you sure this works with Next 13+ App router? Here's my error > > Can you show your...

Still throws same error, `supabase link` did not show any mismatches between local and remote

> In that case, could you create a ticket and report the crash id for me to take a closer look? > > ``` > supabase db reset --create-ticket >...

Sadly, still same error. I'm quite sure it was working fine with older version but I am unable to test which one exactly. Tried `beta` but still got same error...

I think there is a bug, I tried filter results based on nested foreign table key, but without passing `!inner` results were not filtered out properly ```js db.from("products").select(` product_id, suppliers...

I think it can be left as is (no abstraction needed), but I covering this topic (querying foreign tables and filtering through foreign columns) would be extremly helpful. I've spent...

> @ilyabo you should be able to use the `createMiddlewareSupabaseClient`: https://supabase.com/docs/guides/auth/auth-helpers/nextjs#auth-with-nextjs-middleware > > As middleware is always run on the edge: https://nextjs.org/docs/api-reference/edge-runtime > > Which brings up a good point...

I've just stumbled on same issue, that some APIs are stuck with Swagger v2 and to create proper schemas for `openapi-fetch` I had to first parse it to Swagger v3...

You can workaround for this issue using foreign table reference same as in select method ```js const { data, error } = await supabase .from('countries') .select(` name, cities ( name...

This requires PostgREST v11. To force update remote supabase you need to pause it and restore it. To update local supabase, update supabase-cli and restart whole supabase using `stop` and...