2018-09-11 14:11:24 +03:00
|
|
|
Relationships between tables/views
|
|
|
|
==================================
|
|
|
|
To make :doc:`nested object queries <../../queries/nested-object-queries>`, the tables/views in your database need to be
|
|
|
|
connected using relationships.
|
|
|
|
|
|
|
|
Relationships can be of two types:
|
|
|
|
|
|
|
|
- one-to-one or ``object relationships``. For example, one article will have only one author
|
|
|
|
- one-to-many or ``array relationships``. For example, one author can write many articles
|
|
|
|
|
|
|
|
Each relationship has a name which is used to refer to the nested objects in queries. For example, "``articles``" of
|
|
|
|
an ``author`` and "``author``" of an ``article``
|
|
|
|
|
2018-09-12 12:28:55 +03:00
|
|
|
Creating relationships
|
|
|
|
----------------------
|
|
|
|
|
2018-09-11 14:11:24 +03:00
|
|
|
Typically relationships are defined using foreign-key constraints. But in some cases, it might not be possible to
|
|
|
|
use foreign-key constraints to create the relation. For example, while trying to create a relationship involving a view
|
|
|
|
as foreign-keys can't be created on views.
|
|
|
|
|
|
|
|
Here are examples to create relationships using the two methods:
|
|
|
|
|
|
|
|
.. rst-class:: api_tabs
|
|
|
|
.. tabs::
|
|
|
|
|
|
|
|
.. tab:: Using Foreign Keys
|
|
|
|
|
|
|
|
In the previous section, we created two tables, ``author`` and ``article``. Let us now connect these tables to
|
|
|
|
enable nested queries:
|
|
|
|
|
|
|
|
**1) Add foreign-key constraint**
|
|
|
|
|
|
|
|
In the console, navigate to the ``Modify`` tab of the ``article`` table. Edit the ``author_id`` column and configure
|
|
|
|
it as a foreign-key for the ``id`` column in the ``author`` table:
|
|
|
|
|
|
|
|
.. image:: ../../../../img/graphql/manual/schema/add-foreign-key.png
|
|
|
|
|
2018-10-16 09:32:29 +03:00
|
|
|
**2) Create an object relationship**
|
2018-09-11 14:11:24 +03:00
|
|
|
|
|
|
|
Each article has one author. This is an ``object relationship``. The console
|
|
|
|
infers this using the foreign-key and recommends the potential relationship in the ``Relationships`` tab
|
|
|
|
of the ``article`` table.
|
|
|
|
|
|
|
|
Add an ``object relationship`` named ``author`` as shown here:
|
|
|
|
|
|
|
|
.. image:: ../../../../img/graphql/manual/schema/add-1-1-relationship.png
|
|
|
|
|
|
|
|
We can now run a nested object query that is based on this ``object relationship``
|
|
|
|
|
|
|
|
Fetch a list of articles and each article's author:
|
|
|
|
|
|
|
|
.. graphiql::
|
|
|
|
:view_only:
|
|
|
|
:query:
|
|
|
|
query {
|
|
|
|
article {
|
|
|
|
id
|
|
|
|
title
|
|
|
|
author {
|
|
|
|
id
|
|
|
|
name
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
:response:
|
|
|
|
{
|
|
|
|
"data": {
|
|
|
|
"article": [
|
|
|
|
{
|
|
|
|
"id": 1,
|
|
|
|
"title": "sit amet",
|
|
|
|
"author": {
|
|
|
|
"name": "Anjela",
|
|
|
|
"id": 4
|
|
|
|
}
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 2,
|
|
|
|
"title": "a nibh",
|
|
|
|
"author": {
|
|
|
|
"name": "Beltran",
|
|
|
|
"id": 2
|
|
|
|
}
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 3,
|
|
|
|
"title": "amet justo morbi",
|
|
|
|
"author": {
|
|
|
|
"name": "Anjela",
|
|
|
|
"id": 4
|
|
|
|
}
|
|
|
|
}
|
|
|
|
]
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-16 09:32:29 +03:00
|
|
|
**3) Create an array relationship**
|
2018-09-11 14:11:24 +03:00
|
|
|
|
|
|
|
An author can write multiple articles. This is an ``array relationship``.
|
|
|
|
|
|
|
|
You can add an ``array relationship`` exactly how you added an ``object relationship`` as shown above:
|
|
|
|
|
|
|
|
.. image:: ../../../../img/graphql/manual/schema/add-1-many-relationship.png
|
|
|
|
|
|
|
|
We can now run a nested object query that is based on this ``array relationship``.
|
|
|
|
|
|
|
|
Fetch a list of authors and a nested list of each author's articles:
|
|
|
|
|
|
|
|
.. graphiql::
|
|
|
|
:view_only:
|
|
|
|
:query:
|
|
|
|
query {
|
|
|
|
author {
|
|
|
|
id
|
|
|
|
name
|
|
|
|
articles {
|
|
|
|
id
|
|
|
|
title
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
:response:
|
|
|
|
{
|
|
|
|
"data": {
|
|
|
|
"author": [
|
|
|
|
{
|
|
|
|
"id": 1,
|
|
|
|
"name": "Justin",
|
|
|
|
"articles": [
|
|
|
|
{
|
|
|
|
"id": 15,
|
|
|
|
"title": "vel dapibus at"
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 16,
|
|
|
|
"title": "sem duis aliquam"
|
|
|
|
}
|
|
|
|
]
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 2,
|
|
|
|
"name": "Beltran",
|
|
|
|
"articles": [
|
|
|
|
{
|
|
|
|
"id": 2,
|
|
|
|
"title": "a nibh"
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 9,
|
|
|
|
"title": "sit amet"
|
|
|
|
}
|
|
|
|
]
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 3,
|
|
|
|
"name": "Sidney",
|
|
|
|
"articles": [
|
|
|
|
{
|
|
|
|
"id": 6,
|
|
|
|
"title": "sapien ut"
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 11,
|
|
|
|
"title": "turpis eget"
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 14,
|
|
|
|
"title": "congue etiam justo"
|
|
|
|
}
|
|
|
|
]
|
|
|
|
}
|
|
|
|
]
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
.. tab:: Without Foreign Keys
|
|
|
|
|
|
|
|
Let's say you have an ``author`` table and an ``author_avg_rating`` view with fields ``(id, avg)`` which has the
|
|
|
|
average rating of articles for each author.
|
|
|
|
|
|
|
|
To create an ``object relationship`` for the ``author`` table with the ``author_avg_rating`` view, navigate
|
|
|
|
to the ``Relationships`` tab of the ``author`` table in the console and click on the ``+ Add a manual relationship``
|
|
|
|
button:
|
|
|
|
|
|
|
|
.. image:: ../../../../img/graphql/manual/schema/manual-relationship-btn.png
|
|
|
|
|
|
|
|
This will open up a section as shown below:
|
|
|
|
|
|
|
|
.. image:: ../../../../img/graphql/manual/schema/manual-relationship-create.png
|
|
|
|
|
|
|
|
For our case:
|
|
|
|
|
|
|
|
- Relationship Type will be: ``Object Relationship``
|
|
|
|
- Relationship Name can be: ``avg_rating``
|
|
|
|
- Configuration: ``id :: author_avg_rating -> id``
|
|
|
|
|
|
|
|
Now click on the ``Add`` button to create the relationship.
|
|
|
|
|
|
|
|
We can now run a nested object query that is based on this ``object relationship``.
|
|
|
|
|
|
|
|
Fetch a list of authors with the average rating of their articles:
|
|
|
|
|
|
|
|
.. graphiql::
|
|
|
|
:view_only:
|
|
|
|
:query:
|
|
|
|
query {
|
|
|
|
author {
|
|
|
|
id
|
|
|
|
name
|
|
|
|
avg_rating {
|
|
|
|
avg
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
:response:
|
|
|
|
{
|
|
|
|
"data": {
|
|
|
|
"author": [
|
|
|
|
{
|
|
|
|
"id": 1,
|
|
|
|
"name": "Justin",
|
|
|
|
"avg_rating": {
|
|
|
|
"avg": 2.5
|
|
|
|
}
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 2,
|
|
|
|
"name": "Beltran",
|
|
|
|
"avg_rating": {
|
|
|
|
"avg": 3
|
|
|
|
}
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"id": 3,
|
|
|
|
"name": "Sidney",
|
|
|
|
"avg_rating": {
|
|
|
|
"avg": 2.6666666666666665
|
|
|
|
}
|
|
|
|
}
|
|
|
|
]
|
|
|
|
}
|
|
|
|
}
|
2018-09-12 12:28:55 +03:00
|
|
|
|
|
|
|
Renaming relationships
|
|
|
|
----------------------
|
|
|
|
|
|
|
|
To rename a relationship, head to ``Data -> [table-name] -> Relationships`` in the console, drop the existing
|
|
|
|
relationship and recreate it with the new name.
|
|
|
|
|
2018-10-04 07:09:47 +03:00
|
|
|
**Note:** You might not be allowed to drop a relationship if it has been referenced elsewhere (e.g. in a permissions rule).
|