Missing data source leads to "Error: Get config index out of bounds: the len is 1 but the index is 1"

Bug description

I’m following the guide at https://vercel.com/guides/nextjs-prisma-postgres and trying to setup prisma with postgres but after I install next auth and run npx prisma db push I’m getting the error " Error: Get config index out of bounds: the len is 1 but the index is 1"

How to reproduce

Expected behavior

My Understanding is that you are required to proceed with the db being updated without any errors

Prisma information

// schema.prisma

model Post {
  id        Int     @default(autoincrement()) @id
  title     String
  content   String?
  published Boolean @default(false)
  author    User?   @relation(fields: [authorId], references: [id])
  authorId  Int?
}

model User {
  id            Int       @default(autoincrement()) @id
  name          String?
  email         String?   @unique
  emailVerified DateTime? @map(name: "email_verified")
  image         String?
  createdAt     DateTime  @default(now()) @map(name: "created_at")
  updatedAt     DateTime  @updatedAt @map(name: "updated_at")
  posts         Post[]

  @@map(name: "users")
}

model Account {
  id                 Int       @default(autoincrement()) @id
  compoundId         String    @unique @map(name: "compound_id")
  userId             Int       @map(name: "user_id")
  providerType       String    @map(name: "provider_type")
  providerId         String    @map(name: "provider_id")
  providerAccountId  String    @map(name: "provider_account_id")
  refreshToken       String?   @map(name: "refresh_token")
  accessToken        String?   @map(name: "access_token")
  accessTokenExpires DateTime? @map(name: "access_token_expires")
  createdAt          DateTime  @default(now()) @map(name: "created_at")
  updatedAt          DateTime  @default(now()) @map(name: "updated_at")

  @@index([providerAccountId], name: "providerAccountId")
  @@index([providerId], name: "providerId")
  @@index([userId], name: "userId")

  @@map(name: "accounts")
}

model Session {
  id           Int      @default(autoincrement()) @id
  userId       Int      @map(name: "user_id")
  expires      DateTime
  sessionToken String   @unique @map(name: "session_token")
  accessToken  String   @unique @map(name: "access_token")
  createdAt    DateTime @default(now()) @map(name: "created_at")
  updatedAt    DateTime @default(now()) @map(name: "updated_at")

  @@map(name: "sessions")
}

Environment & setup

• OS: Pop OS 20.10
• Database: PostgreSQL
• Node.js version: v12.19.0

Prisma Version

2.23.0

[janpio]

Remaining problem tracked in https://github.com/prisma/prisma/issues/7186

[janpio]

I can reproduce this with prisma validate for any schema missing the datasource block, e.g. an empty schema:

C:\Users\Jan\Documents\throwaway\7343>npx prisma validate
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Error: Get config thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', query-engine\query-engine\src\opt.rs:148:21
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Thanks for reporting this @giordifungula - this is a proper bug we should fix.

(And yes, we make the mistake with prisma.schema vs. schema.prisma all the time ourselves 😆)