How can i use a mode with another comparision?

[char-ptr]

Im trying to lookup a string which is supposed to be case insensitive, in standard prisma you would be able to do something like the following:

prisma.user.findFirst({
where:{
name:{
mode:"insensitive",
equals:"xyz.."
}
}
})

i have now tried to replicate the following in rust, but i don't believe it's possible to chain it hence why it's not working.

prisma.user().find_first(vec![
        prisma::user::name::mode(prisma::_prisma::QueryMode::Insensitive),
        prisma::user::name::equals(name)
    ]).with(....).exec().await.unwrap()

[Brendonovich]

That's interesting, I haven't tested case sensitivity but the code you provided should work. I don't understand what you mean about chaining though?

[char-ptr]

Unfortunately it still doesn't work. i also decided to fork and add an additional test for insensitive finds, it turns out that it might be something at the engine level? as the operation thingy seems to have merged everything fine, here was the output

[src\queries\find_first.rs:163] Operation::Read(selection.build()) = Read(
    Selection {
        name: "findFirstPost",
        alias: Some(
            "result",
        ),
        arguments: [
            (
                "where",
                Object(
                    {
                        "title": Object(
                            {
                                "equals": String(
                                    "test post 1",
                                ),
                                "mode": Enum(
                                    "insensitive",
                                ),
                            },
                        ),
                    },
                ),
            ),
        ],
        nested_selections: [
            Selection {
                name: "id",
                alias: None,
                arguments: [],
                nested_selections: [],
            },
            Selection {
                name: "created_at",
                alias: None,
                arguments: [],
                nested_selections: [],
            },
            Selection {
                name: "updated_at",
                alias: None,
                arguments: [],
                nested_selections: [],
            },
            Selection {
                name: "title",
                alias: None,
                arguments: [],
                nested_selections: [],
            },
            Selection {
                name: "published",
                alias: None,
                arguments: [],
                nested_selections: [],
            },
            Selection {
                name: "views",
                alias: None,
                arguments: [],
                nested_selections: [],
            },
            Selection {
                name: "desc",
                alias: None,
                arguments: [],
                nested_selections: [],
            },
            Selection {
                name: "author_id",
                alias: None,
                arguments: [],
                nested_selections: [],
            },
        ],
    },
)

the reproduce repo can be found here
and the fork can be found here (6.0.0 branch)

[Brendonovich]

I'm suddenly not convinced this is a PCR problem 😅

I tested with a fresh Postgres image in docker, maybe it's a PG version problem?

Also I made a couple of changes to your repo with some QoL improvements 😄

[char-ptr]

I was already using postgres 14.3 (installed via scoop, globally), although oddly enough it does now seem to work when using one from dockerhub. how very strange. i just checked again, and for some reason when i use the old database (from scoop) with prisma for js, it works. i wonder what's going on here?

i made another test repository for the ts code i used, which can be found here

[Brendonovich]

No idea why it's not working on your end, but from what I've tested PCR does support insensitive querying now. Going to close the issue and mark as fixed, but if you have problems with other version of Postgres then please let me know.

[char-ptr]

Alright thank you so much for helping me through this