Drizzle plugin discussion

[hayes]

Now that the drizzle plugin has been updated with RQBv2 support, I am closing out #1027 and moving future discussion about the plugin here, since that thread has gotten long, and has lot's of outdated information.

[josepjaume]

Hello! I've been using the plugin and it greatly simplified my code around pagination. Great job!

However, there's an omission that I'm not being able to find a workaround: row counts on relatedConnection (or drizzleConnection for that matter). I would like to be able to (optionally) get a total number on my connection type, but there seems to be none at the moment. I ended on a dead end while trying to add a field though a second argument on drizzleConnection, but parent always seems to be undefined.

Is there any way I can help?

[hayes]

Thanks for reporting this. There was a bug where the parent wasn't properly passed down into the connection results. Added some test which you can reference as an example for how to implement a total count field here: 0046a00

[josepjaume]

Aaaah awesome! BTW I absolutely love pothos, amazing job! I've used many GraphQL server implementations in many languages and this is the one that wins, hands down!

[MMShep97]

Hey all!

Was going to post an issue but remembered this was here! I've found a solution to my problem, but wanted to post here as info for someone that may stumble upon this as well, and also to get it across the eyes of Hayes if you think something needs to be changed or if you think its good as is!

---

I encountered an error after performing an insert, which I discovered was related to a read-after-write inconsistency wherein drizzle inserted the record into the primary (write) database instance, and, immediately after, performed a read to return the newly created record from the read replica instance. Because of the replication lag between our (aws rds) instances in the cluster (~10-100ms), the read couldn't find the fresh record as it was not yet in the read replica.This resulted in the following error:

Model foo(foo's id) not found

My solution was just to override the specific drizzle query to use the primary db for both the read and write like so:

await db.$primary // $primary is the only addition
.insert(foo)
.values({
    ...values
})
.returning();

After looking into this some more, we've realized that it's actually likely drizzleWithFieldInput that's causing this extra select, as we have an update mutation that's doing very similar logic, but just with fieldWithInput (which does not make an extra select)...

[MMShep97]

Related to

pothos/packages/plugin-drizzle/src/field-builder.ts

Line 75 in 1e9e3db

queryFromInfo({

I'm assuming..? Maybe it needs to respect the database drizzle is using if this select is required?

[hayes]

moving this to a new issue, since I think the answer will be a bit complicated: #1475