[FEATURE]: Add `where` in one-to-one querying

[hstevanoski]

Describe what you want

We're using soft deletions on a product I'm working on (we have deleted_at nullable columns in our tables) and we have to be careful in some instances not to include certain records that have been (soft) deleted. We can easily filter out such deleted_at columns as long as the relation is many-to-many:

const result = await db.query.tableName.findFirst({
  // ...
  with: {
    nToNRelation: {
      // ...
      where: isNull(relationTable.deletedAt),
    },
  },
});

However, when it comes to one-to-one relations this is simply not possible - one gets a TypeScript error: Object literal may only specify known properties, and 'where' does not exist in type [...], i.e., it cannot find the where column in the object.

Yes, in some cases it doesn't make sense to filter on one-to-one relations and it may be a sign of poor database/back-end design decisions, but in other cases it very well does - and the older the software/database tables the harder it is to change how things work. This is a problem because 90% of our database is soft deleted - so the db.query feature is almost useless for us and we have to revert to using db.select, write custom SQL queries, and remember to include the right columns for relations over and over again in each and every query - which, as you can imagine - is error-prone. Please enable such filtering as it hinders even everyday cases like soft deletions.

[jimboboliver]

I think I have a similar case. I have three models, A, B, C. A has many B B has one C

I can't seem to write a query-based call that finds rows of A where C has a particular value (filtered using a 'where' on C).

This doesn't work:

await db.query.A.findMany({
  where: eq(A.id, user.id),
  with: {
    B: {
      with: {
        C: {
          where: isNull(C.endedAt),
        },
      },
    },
  },
});

[SlavenIvanov]

This would be much appreciated!

[issacclee]

same here

[Kokleng-Dev]

same here

[Kokleng-Dev]

1+

[Kokleng-Dev]

1+

[MickL]

This is a duplicate of #3911 - There where works fine and you can use it! Just the typing is wrong. There is even an open PR: https://github.com/drizzle-team/drizzle-orm/pull/4011 But it seems like Drizzle Team never looks into Github issues / PRs?

[ramipellumbi]

Even though this is valid, I recommend you not use it. Instead of omitting the row when the condition does not match, it returns that row with a value of null, which is weird behavior. They need to fix this.

[viniciuspatzer]

1+

[moritzhipper]

1+

[jpsebey]

+1

[AndriiSherman]

Hey everyone!

I've created this message to send in a batch to all opened issues we have, just because there are a lot of them and I want to update all of you with our current work, why issues are not responded to, and the amount of work that has been done by our team over ~8 months.

I saw a lot of issues with suggestions on how to fix something while we were not responding – so thanks everyone. Also, thanks to everyone patiently waiting for a response from us and continuing to use Drizzle!

We currently have 4 major branches with a lot of work done. Each branch was handled by different devs and teams to make sure we could make all the changes in parallel.

---

First branch is drizzle-kit rewrite

All of the work can be found on the alternation-engine branch. Here is a PR with the work done: https://github.com/drizzle-team/drizzle-orm/pull/4439

As you can see, it has 167k added lines of code and 67k removed, which means we've completely rewritten the drizzle-kit alternation engine, the way we handle diffs for each dialect, together with expanding our test suite from 600 tests to ~9k test units for all different types of actions you can do with kit. More importantly, we changed the migration folder structure and made commutative migrations, so you won't face complex conflicts on migrations when working in a team.

What's left here:

• We are finishing handling defaults for Postgres, the last being geometry (yes, we fixed the srid issue here as well).
• We are finishing commutative migrations for all dialects.
• We are finishing up the command, so the migration flow will be as simple as drizzle-kit up for you.

Where it brings us:

• We are getting drizzle-kit into a new good shape where we can call it [email protected]!

Timeline:

• We need ~2 weeks to finish all of the above and send this branch to beta for testing.

Second big branch is a complex one with several HUGE updates

• Bringing Relational Queries v2 finally live. We've done a lot of work here to actually make it faster than RQBv1 and much better from a DX point of view. But in implementing it, we had to make another big rewrite, so we completely rewrote the drizzle-orm type system, which made it much simpler and improved type performance by ~21.4x:

(types instantiations for 3300 lines production drizzle schema + 990 lines relations)

TS v5.8.3: 728.8k -> 34.1k
TS v5.9.2: 553.7k -> 25.4k

You can read more about it here.

What's left here:

• We have 1 issue with TS that is already in progress of being fixed. The issue and Post about fixing.

Where it brings us:

• We are getting drizzle-orm into a new good shape where we can call it [email protected]!

Breaking changes:

• We will have them, but we will have open channels for everyone building on top of drizzle types, so we can guide you through all the changes.

Third branch is adding support for CockroachDB and MSSQL dialects

Support for them is already in the alternation-engine branch and will be available together with the drizzle-kit rewrite.

Summary

All of the work we are doing is crucial and should be done sooner rather than later. We've received a lot of feedback and worked really hard to find the best strategies and decisions for API, DX, architecture, etc., so we can confidently mark it as v1 and be sure we can improve it and remain flexible for all the features you are asking for, while becoming even better for everyone building on top of the drizzle API as well.

We didn't want to stay with some legacy decisions and solutions we had, and instead wanted to shape Drizzle in a way that will be best looking ahead to 2025–2026 trends (v1 will get proper effect support, etc.).

We believe that all of the effort we've put in will boost Drizzle and benefit everyone using it.

Thanks everyone, as we said, we are here to stay for a long time to build a great tool together!

Timelines

We are hoping to get v1 for drizzle in beta this fall and same timeline for latest. Right after that we can go through all of the issues and PRs and resond everyone. v1 for drizzle should close ~70% of all the bug tickets we have, so on beta release we will start marking them as closed!