"invitee" in one-to-one example in drizzle docs wrong?

[hallucinogenizer]

In the one-to-one relationship example in the drizzle docs, the name "invitee" of the relation seems wrong. It should be "inviter", no? The relation is associated with the invitedBy column on the source entity, and points to the id primary key on the target entity. This means that the target is the "inviter". Meaning if you had a user entity and tried to fetch its "invitee", what you would actually get would be the inviter.

I felt this, then I confirmed this and the site's own AI agent says so. Claude also says so.

Conversation with the site's own AI:

**AI:**
Hi!

I'm an AI assistant trained on documentation, help articles, and other content.

Ask me anything about Drizzle ORM.

---
**Me:**
Shouldn't the "invitee" in the `one-to-one` example be named "inviter"?

---

**AI:**
The name "invitee" in the example is correct because it represents the user who was invited (the invitee) by another user[1](https://orm.drizzle.team/docs/relations). This can be seen in the schema where invitedBy points to the ID of the user who did the inviting, and the relation invitee points back to the user who was invited.

Here's the relevant code showing this relationship:

typescript

export const users = pgTable('users', {
	id: serial('id').primaryKey(),
	name: text('name'),
	invitedBy: integer('invited_by'),
});

export const usersRelations = relations(users, ({ one }) => ({
	invitee: one(users, {
		fields: [users.invitedBy],
		references: [users.id],
	}),
}));

The relationship shows that a user has an invitedBy field pointing to another user's ID, and the invitee relation represents the user who was invited by that ID.
Sources
Relations
Docs
[Manage schema](https://orm.drizzle.team/docs/relations)
[Relations](https://orm.drizzle.team/docs/relations)

---

**Me:**
Use this relation in a query. Get a user, and his inviter.

---

**AI:**

Here's how to query a user and their inviter using Drizzle's relational query API:

typescript

const user = await db.query.users.findFirst({
  with: {
    invitee: true
  }
});

[1](https://orm.drizzle.team/docs/rqb#querying)

The result will include both the user's information and their inviter's information through the invitee relation. The inviter's information will be available in the invitee property of the result object.

You can also add filters to find a specific user:

typescript

const user = await db.query.users.findFirst({
  where: (users, { eq }) => eq(users.id, 1),
  with: {
    invitee: true
  }
});

Sources
Query
Docs
[Access your data](https://orm.drizzle.team/docs/rqb)
[Query](https://orm.drizzle.team/docs/rqb)

---

**Me:**
Isn't that wrong? Why would the "inviter" info be in the "invitee" property?

---

**AI:**

You're absolutely right - I apologize for my previous incorrect answer. Looking at the schema:

typescript

export const users = pgTable('users', {
	id: serial('id').primaryKey(),
	name: text('name'),
	invitedBy: integer('invited_by'),
});

export const usersRelations = relations(users, ({ one }) => ({
	invitee: one(users, {
		fields: [users.invitedBy],
		references: [users.id],
	}),
}));

[1](https://orm.drizzle.team/docs/relations)

The relationship is defined as:

    invitedBy column stores the ID of the user who did the inviting
    The invitee relation points from the invited user back to the inviter

So when we query, we would get:

    The current user's record
    In the invitee property, we would get the inviter's information

You're correct that the naming is potentially confusing - while technically correct in terms of the relation direction (the current user is the invitee), it makes the property name counterintuitive when querying. A name like "inviter" might have been clearer for the relation name.