SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

SuperTokens.com

Hello guys. I am getting the following error for some of recipe endpoint: ```ERROR: relation "userid_mapping" does not exist``` Any idea why?

Hi <@264420909169901568> 

Can you share some code for how you are using it?

``` thirdPartySignInUp: async function (input) {
              // TODO: some custom logic
              // or call the default behaviour as show below
              try {
                const created = await originalImplementation.thirdPartySignInUp(input);

                console.log({ created });
                if (created.status === 'OK') {
                  const user = await prisma.thirdparty_users.findFirst({
                    where: {
                      third_party_user_id: input.thirdPartyUserId,
                      third_party_id: input.thirdPartyId,
                    },
                  });
                  if (user) {
                    const balance = await prisma.user_balance.findUnique({
                      where: {
                        user_id: user.user_id,
                      },
                    });
                    if (!balance)
                      await prisma.user_balance.create({
                        data: {
                          user_id: user.user_id,
                          amount: 0,
                        },
                      });
                  }
                }
                return created;
              } catch (e) {
                console.warn(e);
              }
            },```

This is an example of me using a recipe that throws that error

as for version, I think it is the latest? I am using the docker image

it might be that a recent update changed the internal schema and prisma messes it up? Tag is `registry.supertokens.io/supertokens/supertokens-postgresql`

We added a new table in the newer core versions called userid_mapping. But the core should have created that table on its own on start

I think it's my fault then. I am using a prisma schema which was generated based on an older version of supertokens core and now im still aplying it.

Ah right. Well, you can find the latest schema in our docs

Where can I see the releases for that image? I'm thinking of setting the exact version so it doesnt happen in the future with updates and maybe I'll manually upgrade later

See this: https://hub.docker.com/r/supertokens/supertokens-postgresql/tags