upsert does not working with multi unique key.

[hirasaki1985]

Hi, there.

I have a error.
I tried to use upsert function with the multi @@unique key.
Could you please tell me how to deal with it?

schema.prisma

model UserActiveHistorySummary {
  summary_date                 DateTime                        @db.Date
  user_id                      String                          @db.VarChar(255)
  login_count                  Int                             @default(0)
  created_at                   DateTime                        @default(now()) @db.DateTime(0)
  updated_at                   DateTime                        @default(now()) @db.DateTime(0)
  users                        User                            @relation(fields: [user_id], references: [user_id], onDelete: Cascade, map: "fk_uash_user_id_users_user_id")

  @@unique([summary_date, user_id], map: "uq_uahs_summary_date_user_id")
  @@index([summary_date, login_count], map: "idx_uahs_summary_date_login_count")
  @@index([summary_date], map: "idx_uahs_summary_date")
  @@index([user_id], map: "idx_uahs_user_id")

  @@map("user_active_history_summaries")
}

source code

  const prisma = new PrismaClient()

  await prisma.userActiveHistorySummary.upsert({
    where: {
      summary_date_user_id: {
        summary_date: '2022-03-29T00:00:00+09:00',
        user_id: 'shimizu_test',
      },
    },
    create: {
      summary_date: '2022-03-29T00:00:00+09:00',
      user_id: 'shimizu_test',
      login_count: 3,
    },
    update: {
      login_count: 7,
    },
  })

console error

/Users/hirasaki/work/couger/sources/Ludens-analytics/server/node_modules/@prisma/client/runtime/index.js:45582
        throw new PrismaClientUnknownRequestError(message, this.client._clientVersion);
              ^
PrismaClientUnknownRequestError: 
Invalid `prisma.userActiveHistorySummary.upsert()` invocation:


  Query upsertOneUserActiveHistorySummary is required to return data, but found no record(s).
    at Object.request (/Users/hirasaki/work/couger/sources/Ludens-analytics/server/node_modules/@prisma/client/runtime/index.js:45582:15)
    at async PrismaClient._request (/Users/hirasaki/work/couger/sources/Ludens-analytics/server/node_modules/@prisma/client/runtime/index.js:46405:18) {
  clientVersion: '3.12.0'
}

generated table schema.

-- CreateTable
CREATE TABLE `user_active_history_summaries` (
    `summary_date` DATE NOT NULL,
    `user_id` VARCHAR(255) NOT NULL,
    `login_count` INTEGER NOT NULL DEFAULT 0,
    `created_at` DATETIME(0) NOT NULL DEFAULT CURRENT_TIMESTAMP(0),
    `updated_at` DATETIME(0) NOT NULL DEFAULT CURRENT_TIMESTAMP(0),

    INDEX `idx_uahs_summary_date_login_count`(`summary_date`, `login_count`),
    INDEX `idx_uahs_summary_date`(`summary_date`),
    INDEX `idx_uahs_user_id`(`user_id`),
    UNIQUE INDEX `uq_uahs_summary_date_user_id`(`summary_date`, `user_id`)
) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

package.json

  "dependencies": {
    "@prisma/client": "^3.12.0",
  }

[austincrim]

Hey @hirasaki1985 👋 ,

I reproduced this on my end as well (using MySQL) and it does seem unexpected. I'm going to convert this discussion into an issue where our engineering teams will pick it up for investigation.

[hirasaki1985]

@austincrim
thank you!

[moishinetzer]

I'm also coming across this issue, are there any updates re this?

[austincrim]

Any further updates will take place over in this issue. Feel free to add your specific use case, reproduction instructions, or add a 👍.

[remiserougne2017]

Hello,
I have the same issue. Any update ?
Thanks a lot