Aggregate functions returns PGRST100 error

[ahofmeister]

I am following the supabase guide for aggegate functions (https://supabase.com/blog/postgrest-aggregate-functions)

I tried to use it in my project like this

const supabase = createClient(); // see below

const { data, error } = await supabase
.from("transactions")
.select("amount.sum()");

import { createBrowserClient } from "@supabase/ssr";

import { Database } from "@/types/supabase";

export const createClient = () =>
  createBrowserClient<Database>(
    process.env.NEXT_PUBLIC_SUPABASE_URL!,
    process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
  );

This throws following error

{"code":"PGRST100","details":"unexpected '.' expecting letter, digit, \"-\", \"!\", \"(\", \"->>\", \"->\", \"::\", \")\", \",\" or end of input","hint":null,"message":"\"failed to parse select parameter (amount.sum())\" (line 1, column 7)"}

First, I thought it must be the client or something in the project, but I tried the same with calling the API directly like
https://<project_id>.supabase.co/rest/v1/transactions?select=amount.sum()

I also got the same error message.

Can someone please point me in the right direction? I am not sure, which information is needed in order to help me, please ask :)

What I have tried so far / What I understand

• Enabling/Disabling the aggregate functions does not have any impact
• Setting up aggregate functions works in another completely different project
• Restarting the project has no impact
• The setup of the code seems correct, because it also affects calling the API directly

[GaryAustin1]

Did you enable them? Edit bad link: https://supabase.com/blog/postgrest-aggregate-functions#staying-safe-with-aggregate-functions

[ahofmeister]

Yes, I did. But I noticed, that disabling or enabling does not make any difference in the error message.

[ahofmeister]

I tried with a completely different project and it works. I first got the message, to enable the functions and than the correct results.

[ahofmeister]

The PostgREST version was on 10.x.x something. After upgrading it now works as expected. Make sure, to use 12.x.x for PostgREST