`findMany` DateTime queries not finding applicable records

Bug description

This bug was originally reported in https://github.com/RobertCraigie/prisma-client-py/issues/214 but was found to be an internal Query Engine issue as an equivalent Prisma Client query written in TypeScript yields the same unexpected behaviour.

How to reproduce

schema.prisma

// database
datasource db {
  provider = "sqlite"
  url      = "file:database.db"
}

// generator
generator client {
  provider = "prisma-client-js"
}

model Demo {
  id Int @id
  created_at DateTime @default(now())
}

1. prisma db push
2. Open sqlite: sqlite3 database.db
3. Insert the record: INSERT INTO Demo (id) VALUES (1);
4. Confirm the records existence: SELECT * FROM Demo;
5. Run the script below

import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient();

async function main() {
  const today = new Date();
  console.log(today);
  const records = await prisma.demo.findMany({
    where: {
        created_at: {
            lt: today,
        },
    },
  });
  console.log(records);
  console.log(await prisma.demo.findMany())
}

main()
  .catch((e) => {
    throw e;
  })
  .finally(async () => {
    await prisma.$disconnect();
  });

Output:

2022-01-08T11:09:09.035Z
[]
[ { id: 1, created_at: 2022-01-08T10:26:59.000Z } ]

There are more detailed tests included in the original reproduction: https://github.com/iiian/prisma_python_datefailure_demo/blob/master/demo.py

Expected behavior

The record should be found in the first query:

[ { id: 1, created_at: 2022-01-08T10:26:59.000Z } ]

Environment & setup

• OS: Mac OS
• Database: SQLite
• Node.js version: v17.1.0

Prisma Version

prisma                  : 3.7.0
@prisma/client          : 3.7.0
Current platform        : darwin
Query Engine (Node-API) : libquery-engine 8746e055198f517658c08a0c426c7eec87f5a85f (at node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine        : migration-engine-cli 8746e055198f517658c08a0c426c7eec87f5a85f (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core 8746e055198f517658c08a0c426c7eec87f5a85f (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt 8746e055198f517658c08a0c426c7eec87f5a85f (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : 8746e055198f517658c08a0c426c7eec87f5a85f
Studio                  : 0.445.0

[RobertCraigie]

Also should be noted that this bug does not occur when the record is created within Prisma, for example:

import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient();

function sleep(ms: number) {
  return new Promise((resolve) => setTimeout(resolve, ms));
}

async function main() {
  await prisma.demo.create({
    data: {
        id: 1,
    },
  });
  await sleep(2000);
  const today = new Date();
  console.log(today);
  const records = await prisma.demo.findMany({
    where: {
      created_at: {
        lt: today,
      },
    },
  });
  console.log(records);
  console.log(await prisma.demo.findMany());
}

main()
  .catch((e) => {
    throw e;
  })
  .finally(async () => {
    await prisma.$disconnect();
  });

Output:

2022-01-09T12:14:48.585Z
[ { id: 1, created_at: 2022-01-09T12:14:46.565Z } ]
[ { id: 1, created_at: 2022-01-09T12:14:46.565Z } ]

Using raw queries causes the original error:

- await prisma.demo.create({
-     data: {
-         id: 1,
-     },
-   });
+ await prisma.$queryRaw`INSERT INTO Demo (id) VALUES (1);`

[iiian]

Not an issue for MySQL.