The relations field needs to be manually added. For example:

const userResolver = resolver.of(users, {
  me: query(users).resolve(() => db.select().from(users).then(res => res[0]))

  sessions: usersResolverFactory.relationField("sessions"),
})

This allows us to ignore complex relational queries when writing custom queries and mutations. GQLoom will use Dataloader to load data behind the scenes.

There is another important reason: drizzle does not store relationship metadata in the 'users' table internally. Without using a drizzleResolverFactory that accepts full db objects, it is difficult for GQLoom to know that the 'users' table has a relationship field called 'sessions'.

I'm currently considering how to automatically generate select parameters based on GraphQL queries so that we can precisely retrieve the right amount of data from the database. After this feature is completed, perhaps we can directly add relational fields to UsersItem. However, this means that we need to explicitly call a useSelectiveFields() for all mutation or query that return entities. The API might look like this:

const userResolver = resolver.of(users, {
  me: query(users)
    .resolve(async() => {
      const [me] = await db.select(useSelectiveFields(users)).from(users)
      return me
    })
})

Drizzle Relational API v2 #28

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions