Practical GraphQL - Become a GraphQL Ninja - Type Relationships in GraphQL

What is the primary goal when establishing relationships between types in GraphQL?

• To associate each car with a user

• To ensure each car has a unique identifier

• To list all cars in alphabetical order

• To create a separate database for cars

Why should the owner field in the car type be non-nullable?

• To ensure every car has a user

• To allow cars to exist without users

• To improve the performance of queries

• To make the database more flexible

What change is made to the data model to link cars to users?

• Using a string to represent the owner

• Creating a separate table for ownership

• Introducing a property called 'owned by' with an ID

• Adding a new field called 'ownerName'

What issue arises when using the default resolver for the car owner field?

• It returns a string instead of a user type

• It fails to return any data

• It returns a number instead of a user type

• It causes a syntax error

How does the custom resolver help in fetching the correct user data?

• By converting the ID to a string

• By ignoring the 'owned by' property

• By directly accessing the user database

• By using the 'owned by' ID to fetch user details

What is the purpose of logging the parent parameter in the custom resolver?

• To verify the fields returned from the car type

• To test the speed of the resolver

• To ensure the console is working

• To check if the parent is null

What adjustment is necessary when using the 'owned by' ID to access the user array?

• Dividing the ID by two

• Multiplying the ID by two

• Adding one to the ID

• Subtracting one from the ID