Cannot read properties of undefined (reading 'referencedTable')

[maxpaleo]

Hi guys, I've been running into an issue I haven't come across before, and despite a few hours of trying to locate the issue I am not able to identify it.

I keep on running into an error:

Cannot read properties of undefined (reading 'referencedTable')

When trying to query a table with its relation. I am performing a query.findMany and then including the with which is a reference to the reference set up in schema.

I have this setup with other tables in the db and they don't cause issues, yet this one does. And in Drizzle studio the relation also correctly shows.

The query

• As long as I remove the with I don't run into the error.

The table schema

The referenced table

• Contains an id column

I tried to look up the issue online and found several people that faced the same issue, but none of them seemed to have been resolved.

I've considered creating a separate table for the join only, but I don't see why this would be necessary, since I don't need any additional table properties as part of the relation alone.

[SantiagoZarate]

Hi, i'd been running into the same problem until i've figured out that i wasn't exporting the relations object.

My tables:

Barrel file where i export my schemas:

DB client creation file:

I hope exporting the relations object fixes your problem ^^

[samuelwhunter]

Just to expand on this if anyone's looking. Drizzle was automatically creating a relations and schema file in the migrations folder based on an existing db. You have to do this in your db client creation file to combine the two:

import * as schema from './schema';
import * as relations from './relations';
import { drizzle } from 'drizzle-orm/...';

const db = drizzle(client, { schema: { ...schema, ...relations } });

[zhixXiang]

thank you for this!

[andyngdz]

Thanks, this doesn't mention anywhere in the docs 🙄

[Jac0xb]

Docs are not great

[s1n7ax]

Man, I was this close to ditching development and starting a career in farming

[webothdo]

thanks for this answer man, got it through their AI but I really think this is something that should be added to the documentation

[ViggoV]

I am having a the same problem as OP, and the suggested solutions aren't applicable, since I am using an older version of Drizzle which does not export the relations seperately (The reason is, that the newer versions have changed the way objects are named when using a specific schema, when introspecting. This would breaks my entire codebase and I haven't gotten any responses to my issue on the subject)

According to the scarce information I've been able to find, a .references(...) call on the column should automatically create a relation

[ingridkindem]

If you've read through all these discussions, tried everything, and still feel like you've done everything right according to the docs—you're probably not wrong. In my case, I had a monorepo with a separate db folder and simply forgot to build it. Hopefully, this saves someone from hours of debugging 🤡