graphql-engine/server/tests-py/queries/graphql_query/aggregations/setup.yaml
Vladimir Ciobanu 6e752a7876 server: add type information to aggregates and stringify them (closes #5704)
Fixes https://github.com/hasura/graphql-engine/issues/5704 by checking, for aggregate fields whether we are handling a numeric aggregation.

This PR also adds type information to `ColFld` such that we know the type of the field.

This is the second attempt. See #319 for a less invasive approach. @nicuveo suggested type information might be useful, and since it wasn't hard to add, I think this version is better as well.

GitOrigin-RevId: aa6a259fd5debe9466df6302839ddbbd0ea659b5
2021-01-18 13:52:51 +00:00

84 lines
1.5 KiB
YAML

type: bulk
args:
#Author table
- type: run_sql
args:
sql: |
create table author(
id serial primary key,
name text unique
);
CREATE TABLE article (
id SERIAL PRIMARY KEY,
title TEXT,
content TEXT,
author_id INTEGER REFERENCES author(id),
is_published BOOLEAN,
read_time NUMERIC,
published_on TIMESTAMP NOT NULL DEFAULT NOW()
);
insert into author (name)
values
('Author 1'),
('Author 2');
insert into article (title,content,author_id,is_published,read_time,published_on)
values
(
'Article 1',
'Sample article content 1',
1,
false,
1.5,
'1999-01-08 04:05:06'
),
(
'Article 2',
'Sample article content 2',
1,
true,
3.3,
'1999-01-08 04:05:07'
),
(
'Article 3',
'Sample article content 3',
2,
true,
7.8,
'1999-01-09 04:05:06'
);
- type: track_table
args:
schema: public
name: author
#Article table
- type: track_table
args:
schema: public
name: article
#Object relationship
- type: create_object_relationship
args:
table: article
name: author
using:
foreign_key_constraint_on: author_id
#Array relationship
- type: create_array_relationship
args:
table: author
name: articles
using:
foreign_key_constraint_on:
table: article
column: author_id
#Insert values