Bknd Relationship Designer FAQs

Question 1

How do I customize foreign key names in Bknd?

Accepted Answer

By default, Bknd uses the target entity name (e.g., users_id), but you can use the 'mappedBy' option in your schema definition to specify a custom name like 'author_id'.

Question 2

How do I load related data in a single query?

Accepted Answer

You can use the 'with' property in your data fetching logic (e.g., api.data.readMany('posts', { with: { users: true } })) to eager-load related records.

Question 3

Does this skill support many-to-many relationships?

Accepted Answer

Yes, it provides patterns for many-to-many associations, including how to automatically generate junction tables or add extra fields like 'created_at' to the connection table.

Question 4

Can I define relationships in the UI instead of code?

Accepted Answer

Yes, the skill includes a detailed UI approach for non-developers or quick prototyping using the Bknd local dashboard at localhost:1337.

Question 5

What is the difference between relation() and .references()?

Accepted Answer

The relation() helper is more robust, supporting inverse navigation and many-to-many links, while .references() is a simpler shorthand for creating basic foreign keys on a number field.

Bknd Relationship Designer

About

Key Features

Use Cases

Bknd Relationship Designer

About

Key Features

Use Cases