{% endhint %}
### Ordering (`$order`)
You can define a list of fields that you want to use for ordering
```graphql
query Movimientos($where: JSON, $limit: Int, $offset: Int) {
MovimientosAndCount(
where: $where
order: [["Fecha", "desc"]] //order desc by Date
limit: $limit
offset: $offset
) {
items {
Id
Fecha
Descripcion
}
total
}
}
query Movimientos() {
MovimientosAndCount(
order: [["Fecha", "desc"], ["Descripcion", "asc"]] //order desc by Date and Description
) {
items {
Id
Fecha
Descripcion
}
total
}
}
```
#### **Ordering by Child Properties (Attributes)**
To order a query result by a child property (attribute) of an associated model, you can use the `order` option in Sequelize. This option takes an array of items, each representing a column to order by and its direction (ascending or descending). Here’s how you can do it:
query getUserDataApp {
Usuarios(
order: [["UsuariosXEmpresas", "EmpresaSeleccionada", "desc"]]) {
Id
Nombre
Correo
Apellidos
Foto
Identificacion
UsuariosXEmpresas {
EmpresaFK
EmpresaSeleccionada
Empresa {
Nombre
}
}
}
}
### Query Options (`$queryOptions`)
By default, all join clauses in Codenull are "`LEFT OUTER JOIN`". However you can overwrite this behavior. This parameter is optional.
You can customize the following options in the `queryOptions` parameter:
| Option | | Default Value |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------- |
| `required` | When `true` all joins will be handle as "`INNER JOIN`" | false |
| `includeOptions` | Allows to set Inner or left join at table level. This is an array with `model and` `required` props like this `{ model: "Role", required: true}` | null |
{% hint style="info" %}
This will return different sets of data depending on how you configure, be aware of the configuration you are defining.
{% endhint %}
```graphql
# This will return all users where the role is Admin
query {
UsuariosAndCount(
queryOptions: {
required: false
includeOptions: [{ model: "Rol", required: true }]
}
where: {
includeFilter: {
RolesxUsuarios: { includeFilter: { Rol: { Nombre: "Admin" } } }
}
}
) {
items {
Nombre
RolesxUsuarios {
Rol {
Nombre
}
}
}
}
}
#resulting query, pay attention to the left join and inner joins
# SELECT
# [Usuarios].*,
# [RolesxUsuarios].[Id] AS [RolesxUsuarios.Id],
# [RolesxUsuarios->Rol].[Nombre] AS [RolesxUsuarios.Rol.Nombre],
# [RolesxUsuarios->Rol].[Id] AS [RolesxUsuarios.Rol.Id]
# FROM
# (
# SELECT
# [Usuarios].[Nombre],
# [Usuarios].[Id]
# FROM
# [Usuarios] AS [Usuarios]
# WHERE
# (
# SELECT
# [RolesxUsuarios].[UsuarioId]
# FROM
# [RolesxUsuarios] AS [RolesxUsuarios]
# INNER JOIN [Roles] AS [Rol] ON [RolesxUsuarios].[RoleId] = [Rol].[Id]
# AND [Rol].[Nombre] = N'Admin'
# WHERE
# ([RolesxUsuarios].[UsuarioId] = [Usuarios].[Id])
# ORDER BY
# [RolesxUsuarios].[Id] OFFSET 0 ROWS FETCH NEXT 1 ROWS ONLY
# ) IS NOT NULL
# ORDER BY
# [Usuarios].[Id] OFFSET 0 ROWS FETCH NEXT 100 ROWS ONLY
# ) AS [Usuarios]
# LEFT OUTER JOIN (
# [RolesxUsuarios] AS [RolesxUsuarios]
# INNER JOIN [Roles] AS [RolesxUsuarios->Rol] ON [RolesxUsuarios].[RoleId] = [RolesxUsuarios->Rol].[Id]
# AND [RolesxUsuarios->Rol].[Nombre] = N'Admin'
# ) ON [Usuarios].[Id] = [RolesxUsuarios].[UsuarioId];
```
The next configuration produces a different result.
```graphql
# This will return all users but only will join roles whose name is "Admin"
# If the role is not "Admin", it will still return the user but the role will be null
query {
UsuariosAndCount(
queryOptions: {
required: true
includeOptions: [{ model: "Rol", required: false }]
}
where: {
includeFilter: {
RolesxUsuarios: { includeFilter: { Rol: { Nombre: "Admin" } } }
}
}
) {
items {
Nombre
RolesxUsuarios {
Rol {
Nombre
}
}
}
}
}
#resulting query, pay attention to the left join and inner joins
# SELECT
# [Usuarios].*,
# [RolesxUsuarios].[Id] AS [RolesxUsuarios.Id],
# [RolesxUsuarios->Rol].[Nombre] AS [RolesxUsuarios.Rol.Nombre],
# [RolesxUsuarios->Rol].[Id] AS [RolesxUsuarios.Rol.Id]
# FROM
# (
# SELECT
# [Usuarios].[Nombre],
# [Usuarios].[Id]
# FROM
# [Usuarios] AS [Usuarios]
# WHERE
# (
# SELECT
# [UsuarioId]
# FROM
# [RolesxUsuarios] AS [RolesxUsuarios]
# WHERE
# ([RolesxUsuarios].[UsuarioId] = [Usuarios].[Id])
# ORDER BY
# [RolesxUsuarios].[Id] OFFSET 0 ROWS FETCH NEXT 1 ROWS ONLY
# ) IS NOT NULL
# ORDER BY
# [Usuarios].[Id] OFFSET 0 ROWS FETCH NEXT 100 ROWS ONLY
# ) AS [Usuarios]
# INNER JOIN [RolesxUsuarios] AS [RolesxUsuarios] ON [Usuarios].[Id] = [RolesxUsuarios].[UsuarioId]
# LEFT OUTER JOIN [Roles] AS [RolesxUsuarios->Rol] ON [RolesxUsuarios].[RoleId] = [RolesxUsuarios->Rol].[Id]
# AND [RolesxUsuarios->Rol].[Nombre] = N'Admin'
```
#### Query Options with multiple relations with the same table
If I have a table with several ties with the same table I should define the model name in the query options with the same name as the auto-generated name by codenull. For instance:
```graphql
query getOrdenes($offset: Int, $limit: Int, $where: JSON) {
Ordenes: OrdenesAndCount(
where: $where
offset: $offset
limit: $limit
#The name of the model is the same as the name of the field to be returned "UnidadNegocio__UnidadNegocioFK"
queryOptions: {includeOptions: [ {model: "UnidadNegocio__UnidadNegocioFK", required: true}]}
) {
items {
Id
UnidadNegocioFK
UnidadNegocio__UnidadNegocioFK {
Nombre
}
UnidadNegocioActualFK
}
total
}
}
```
[^1]:
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://codenull.gitbook.io/dev/configurations/components/datasources/fetching-data.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.