Open shuther opened 3 months ago
@shuther What version of postgres are you running ?
I used the managed service offer (free for now) from https://xata.io/; my guess is that something was missing during the migration. happy to start again from a fresh start if I can help you to debug it?
How did you run the migration ?
I found the problem, the error message was misleading (the table exists); and I am not sure if the problem is on the xata side, prisma or somewhere else. pg_catalog.obj_description is expected an OID as per postgres16 doc , but it is called using ('"' || "table_schema" || '"."' || "table_name" || '"') and it seems to work ok. However the cast (:regclass) is not accepted when it is called in a particular way. I tested it with cast(xxx as regclass) but not sucess neither.
pg_catalog.obj_description('public.jackson_ttl'::regclass, 'pg_class') is working. pg_catalog.obj_description('"public"."jackson_ttl"'::regclass, 'pg_class') is also working ('"' || "table_schema" || '"."' || "table_name" || '"')::regclass as c is NOT working
I will open a bug with xata as it sounds an issue with their postgresql server.
Just starting the template,
in .env I have:
npx prisma db push
did not return any error.I am able to signup an account, but when I click on Settings/Single Sign-On, I have the error below:
I would have expected the tables to be setup.