Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MongoDb] Query logger produces incorrect output #15467

Closed
do4gr opened this issue Sep 22, 2022 · 0 comments · Fixed by prisma/prisma-engines#3321
Closed

[MongoDb] Query logger produces incorrect output #15467

do4gr opened this issue Sep 22, 2022 · 0 comments · Fixed by prisma/prisma-engines#3321
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. team/client Issue for team Client. topic: logging topic: mongodb
Milestone

Comments

@do4gr
Copy link
Member

do4gr commented Sep 22, 2022

In some cases, here an update with many fields, the output of the logger for Mongo is not immediately valid to try manually. It often works but not for all cases. Here is an example missing comma separators.

db.Standing.updateMany({
    _id: {
        $in: [
            ObjectId("632a0fd5392630a54d36fcba"),
        ],
    },
}, [
{
    $set: {
        leagueId: {
            $literal: 2363725,
        },
    },
}{
    $set: {
        teamId: {
            $literal: 972030012,
        },
    },
}{
    $set: {
        awayLosses: {
            $literal: 0,
        },
    },
}{
@do4gr do4gr added topic: mongodb bug/2-confirmed Bug has been reproduced and confirmed. team/client Issue for team Client. labels Sep 22, 2022
@janpio janpio added kind/bug A reported bug. topic: logging labels Sep 22, 2022
@janpio janpio added this to the 4.6.0 milestone Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. team/client Issue for team Client. topic: logging topic: mongodb
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants