matsyui Posts - Answer Overflow

matsyui

•Created by matsyui on 3/27/2025 in #help-and-questions

Prisma db pull Extremely Slow on Supabase with Custom Schema

Issue: Prisma db pull is extremely slow when introspecting a schema on Supabase. Details:
- Using PostgreSQL on Supabase
- Prisma version:

prisma                  : 5.17.0
@prisma/client          : 5.17.0
Computed binaryTarget   : windows
Operating System        : win32
Architecture            : x64
Node.js                 : v22.14.0
Query Engine (Node-API) : libquery-engine 393aa359c9ad4a4bb28630fb5613f9c281cde053 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Schema Engine           : schema-engine-cli 393aa359c9ad4a4bb28630fb5613f9c281cde053 (at node_modules\@prisma\engines\schema-engine-windows.exe)
Schema Wasm             : @prisma/prisma-schema-wasm 5.17.0-31.393aa359c9ad4a4bb28630fb5613f9c281cde053
Default Engines Hash    : 393aa359c9ad4a4bb28630fb5613f9c281cde053
Studio                  : 0.502.0
Preview Features        : multiSchema

prisma                  : 5.17.0
@prisma/client          : 5.17.0
Computed binaryTarget   : windows
Operating System        : win32
Architecture            : x64
Node.js                 : v22.14.0
Query Engine (Node-API) : libquery-engine 393aa359c9ad4a4bb28630fb5613f9c281cde053 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Schema Engine           : schema-engine-cli 393aa359c9ad4a4bb28630fb5613f9c281cde053 (at node_modules\@prisma\engines\schema-engine-windows.exe)
Schema Wasm             : @prisma/prisma-schema-wasm 5.17.0-31.393aa359c9ad4a4bb28630fb5613f9c281cde053
Default Engines Hash    : 393aa359c9ad4a4bb28630fb5613f9c281cde053
Studio                  : 0.502.0
Preview Features        : multiSchema

- Debug logs show it gets stuck at:

PS D:\Gitlab\Project - Copy> prisma db pull
Prisma schema loaded from prisma\schema.prisma
Environment variables loaded from .env
Datasource "db": PostgreSQL database "postgres", schemas "project-schema" at "aws-0-us-east-1.pooler.supabase.com:6543"

⠼ Introspecting based on datasource defined in prisma\schema.prisma

PS D:\Gitlab\Project - Copy> prisma db pull
Prisma schema loaded from prisma\schema.prisma
Environment variables loaded from .env
Datasource "db": PostgreSQL database "postgres", schemas "project-schema" at "aws-0-us-east-1.pooler.supabase.com:6543"

⠼ Introspecting based on datasource defined in prisma\schema.prisma

Has anyone faced this before? Any fixes?

14 replies

PPrisma

•Created by matsyui on 7/22/2024 in #help-and-questions

Not updating types

6 replies

PPrisma

•Created by matsyui on 6/19/2024 in #help-and-questions

Invalid `prisma.account.findUnique()` invocation:

I am having issues with the google signin redirecting me to http://localhost:3000/api/auth/error?error=AdapterError Here's the error log:

[auth][error] AdapterError: Read more at https://errors.authjs.dev#adaptererror
[auth][cause]: PrismaClientValidationError:
Invalid `prisma.account.findUnique()` invocation:

{
  where: {
    provider_providerAccountId: {
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
      providerAccountId: "XXXXXXXXXXXXXXXXXXXXXXXXXXX",
      provider: "google"
    },
?   id?: Int,
?   providerId_providerAccountId?: accountProviderIdProviderAccountIdCompoundUniqueInput,
?   AND?: accountWhereInput | accountWhereInput[],
?   OR?: accountWhereInput[],
?   NOT?: accountWhereInput | accountWhereInput[],
?   userId?: IntFilter | Int,
?   providerType?: StringFilter | String,
?   providerId?: StringFilter | String,
?   providerAccountId?: StringFilter | String,
?   refreshToken?: StringNullableFilter | String | Null,
?   accessToken?: StringNullableFilter | String | Null,
?   accessTokenExpires?: DateTimeNullableFilter | DateTime | Null,
?   createdAt?: DateTimeFilter | DateTime,
?   updatedAt?: DateTimeFilter | DateTime,
?   user?: UserRelationFilter | userWhereInput
  },
  select: {
    user: true
  }
}

Unknown argument `provider_providerAccountId`. Did you mean `providerId_providerAccountId`? Available options are marked with ?.

[auth][error] AdapterError: Read more at https://errors.authjs.dev#adaptererror
[auth][cause]: PrismaClientValidationError:
Invalid `prisma.account.findUnique()` invocation:

{
  where: {
    provider_providerAccountId: {
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
      providerAccountId: "XXXXXXXXXXXXXXXXXXXXXXXXXXX",
      provider: "google"
    },
?   id?: Int,
?   providerId_providerAccountId?: accountProviderIdProviderAccountIdCompoundUniqueInput,
?   AND?: accountWhereInput | accountWhereInput[],
?   OR?: accountWhereInput[],
?   NOT?: accountWhereInput | accountWhereInput[],
?   userId?: IntFilter | Int,
?   providerType?: StringFilter | String,
?   providerId?: StringFilter | String,
?   providerAccountId?: StringFilter | String,
?   refreshToken?: StringNullableFilter | String | Null,
?   accessToken?: StringNullableFilter | String | Null,
?   accessTokenExpires?: DateTimeNullableFilter | DateTime | Null,
?   createdAt?: DateTimeFilter | DateTime,
?   updatedAt?: DateTimeFilter | DateTime,
?   user?: UserRelationFilter | userWhereInput
  },
  select: {
    user: true
  }
}

Unknown argument `provider_providerAccountId`. Did you mean `providerId_providerAccountId`? Available options are marked with ?.

6 replies

Gaming

Programming