Defining relations of schemas in separate files

[vexCoder]

How to declare relations if the schema objects are on different files? for example id like to declare a member schema and it has an activeAddress foreign key and then on another file the address schema with member foreign key. im getting cyclic dependency issues doing the examples in the docs.

[hyunbinseo]

Please provide a reproduction of the cyclic dependency issue.

📦 <project root>
└ 📂 src
└ 📂 db
   └ 📂 schema
      ├ 📜 address.ts
      └ 📜 member.ts

// member.ts

import { integer, sqliteTable } from 'drizzle-orm/sqlite-core';
import { address } from './address';

export const memberTable = sqliteTable('member', {
  id: integer('id').primaryKey(),
  activeAddress: integer('active_address')
    .notNull()
    .references(() => address.id),
});

[halilhanbadem]

Yes, there is a problem with this. I think the best way is to have the entire schema system in a single file, but this can also lead to complexity.

📦 <project root>
└ 📂 src
└ 📂 db
   └ 📂 schema
      ├ 📜 user.js
      └ 📜 company.js
      └ 📜 posts.js

Consider a structure like this. The company table is related to the user table. In this case, a relations definition is required in the company table. At the same time, relations should be defined in the user table. In this case, the two files will call each other and a cyclic dependency issue will occur. Does anyone have any ideas about this?

[vexCoder]

@hyunbinseo basically this

[halilhanbadem]

@vexCoder, I used the same approach as I did in Sequelize and it worked. For schemas made using multiple files, all relations operations should be done in a single file. In short;

So I guess we just need to keep all the relations transactions in a single file.

@AndriiSherman shouldn't the documentation be improved on this subject? All the documentation goes through a single schema file, it's a bit confusing