can't use date type as primary key

Bug description

If mysql date type field is not a primary key, the create function will success. But define a Composite Primary Key with Integer and Date, will cause an error

How to reproduce

CREATE TABLE `test`  (
  `test_id` int(11) NOT NULL,
  `test_day` date NOT NULL,
  PRIMARY KEY (`test_id`, `test_day`) USING BTREE
);

import prisma from './src/prisma'

async function create() {
  await prisma.test.create({data: {testId: 1, testDay: new Date()}})
}

create()

output:

BEGIN []
INSERT INTO `testdb`.`test` (`test_id`,`test_day`) VALUES (?,?) [1,2021-08-27 16:00:00 UTC]
SELECT `testdb`.`test`.`test_id`, `testdb`.`test`.`test_day` FROM `testdb`.`test` WHERE (`testdb`.`test`.`test_id` = ? AND `testdb`.`test`.`test_day` = ?) LIMIT ? OFFSET ? [1,2021-08-27 16:00:00 UTC,1,0]
ROLLBACK []
BEGIN []
INSERT INTO `testdb`.`test` (`test_id`,`test_day`) VALUES (?,?) [1,2021-08-27 16:00:00 UTC]
SELECT `testdb`.`test`.`test_id`, `testdb`.`test`.`test_day` FROM `testdb`.`test` WHERE (`testdb`.`test`.`test_id` = ? AND `testdb`.`test`.`test_day` = ?) LIMIT ? OFFSET ? [1,2021-08-27 16:00:00 UTC,1,0]
ROLLBACK []
BEGIN []
INSERT INTO `testdb`.`test` (`test_id`,`test_day`) VALUES (?,?) [1,2021-08-27 16:00:00 UTC]
SELECT `testdb`.`test`.`test_id`, `testdb`.`test`.`test_day` FROM `testdb`.`test` WHERE (`testdb`.`test`.`test_id` = ? AND `testdb`.`test`.`test_day` = ?) LIMIT ? OFFSET ? [1,2021-08-27 16:00:00 UTC,1,0]
ROLLBACK []
/Users/wis/Workspaces/testdb/testprisma/node_modules/@prisma/client/runtime/index.js:36437
        throw new import_engine_core3.PrismaClientUnknownRequestError(message, this.client._clientVersion);
              ^

PrismaClientUnknownRequestError3 [PrismaClientUnknownRequestError]: 
Invalid `prisma.test.create()` invocation:


  Query createOneTest is required to return data, but found no record(s).
    at RequestHandler.request (/Users/wis/Workspaces/testdb/testprisma/node_modules/@prisma/client/runtime/index.js:36437:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  clientVersion: '2.30.0'
}

Expected behavior

No response

Prisma information

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["interactiveTransactions"]
}

datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
}

model Test {
  testId  Int      @map("test_id")
  testDay DateTime @db.Date @map("test_day")

  @@id([testId, testDay])
  @@map("test")
}

Environment & setup

• OS: Mac OS
• Database: MySQL
• Node.js version: v16.6.1

Prisma Version

prisma                : 2.30.0
@prisma/client        : 2.30.0
Current platform      : darwin
Query Engine (Binary) : query-engine 60b19f4a1de4fe95741da371b4c44a92f4d1adcb (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine      : migration-engine-cli 60b19f4a1de4fe95741da371b4c44a92f4d1adcb (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine  : introspection-core 60b19f4a1de4fe95741da371b4c44a92f4d1adcb (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary         : prisma-fmt 60b19f4a1de4fe95741da371b4c44a92f4d1adcb (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash  : 60b19f4a1de4fe95741da371b4c44a92f4d1adcb
Studio                : 0.422.0
Preview Features      : interactiveTransactions

[shankuljain]

FWIW, As mentioned in #10378 , the workaround is removing milliseconds.

async function create() {
  await prisma.test.create({data: {testId: 1, testDay: new Date(new Date().setMilliseconds(0))}})
}

I knew this is a solution. And I use moment().startOf(‘day’) to resolve this problem. But if the api is designed by this way, for developers, WTF…

Agreed, just wanted to put this so other folks don’t have to figure out themselves like I did.

[wvq]

If you close the issue, we won’t be able to track this and fix it. We are people and we make mistakes (or overlook details).

I’m sorry, commented yestoday, maybe click the wrong button.