clarification on using aggregates with limit argument

subscription{
  suppliers_aggregate(limit:10){
    nodes{
      name
    }
    aggregate{
     count
    }
  }
} 

it still limit the aggregate query

SELECT
  json_build_object(
    'nodes',
    coalesce(json_agg("nodes"), '[]'),
    'aggregate',
    json_build_object('count', COUNT(*))
  ) AS "root"
FROM
  (
    SELECT
      1 AS "root__one",
      row_to_json(
        (
          SELECT
            "_1_e"
          FROM
            (
              SELECT
                "_0_root.base"."name" AS "name"
            ) AS "_1_e"
        )
      ) AS "nodes"
    FROM
      (
        SELECT
          *
        FROM
          "public"."suppliers"
        WHERE
          ('true')
      ) AS "_0_root.base"
    LIMIT
      10
  ) AS "_2_root"

heres the generated query. it doesnt define the only the node get to be limit

[revskill10]

@shahidhk I think the expected behaviour should be:

• Limit is used to fetch real data rows.
• Aggregate count is to calculate Total rows number of the table, independent of limit

So,

subscription {
  suppliers_aggregate(limit:10) {
    aggregate { count }    
  }
} 

should fetch 10 rows of data, but aggregate.count returns Total number of rows of that table based on permission.

[shahidhk]

@zesterquinn Since you’re adding the limit argument, this is the expected behaviour. If your intention is to get 10 items and also get the total count, you have to use two subscriptions:

# get 10 items
subscription {
  suppliers(limit:10) {
    name
  }
} 

# get the total count
subscription {
  suppliers_aggregate {
    aggregate{
     count
    }
  }
}