Cannot order by multiple columns

[justinsunyt]

Bug report

Describe the bug

When trying to order multiple columns by using multiple .order() modifiers on a select function, the result only orders by the first column specified.

To Reproduce

Here is my code to get some rows from a table, which is then ordered first by last_chatted and then by created_at.

response = (
    supabase.table("clones")
    .select("*")
    .eq("owner", uid)
    .order("last_chatted", desc=True)
    .order("created_at", desc=True)
    .execute()
)

Expected behavior

The response should be ordered by last_chatted, and then created_at. However, this is not the case and the result is only ordered by last_chatted. I have confirmed that when I only order by last_chatted and created_at separately the code works as expected. I have also confirmed using the sort by visualization on my Supabase dashboard that the chained ordering is different from the result I get.

System information

• OS: macOS
• supabase: 2.4.2

Additional context

The same issue was reported in Discord in December, but no GitHub issue was created.

[silentworks]

What results do you get when you run this same query in the SQL editor? from my tests I get the same result from the SQL editor and the library. Here is the SQL equivalent of your code above:

SELECT *
FROM "public"."clones"
WHERE "owner" = 'your_uid_here'
ORDER BY "last_chatted" DESC, "created_at" DESC;

[silentworks]

Closing this out as there has been no reply in over a month.

[Nikdedov]

@justinsunyt
Faced same problem, and the issue is with postgrest-py not with supabase-py.
My workaround using your example:

request_build=
    supabase.table("clones")
    .select("*")
    .eq("owner", uid)
    .order("last_chatted", desc=True)
    .order("created_at", desc=True)

#get list of all added orders
removed_orders=request_build.params.get_list('order')

#remove them from QueryParams
request_build.params=request_build.params.remove('order')

#add back by merging them
request_build.params=request_build.params.add('order',','.join(removed_orders))
response =request_build.execute()

The problem is that adding several orders generates for QueryParams something like this: &order=last_chatted.desc&order=created_at.desc , but according to postgrest docs it should look like: &order=last_chatted.desc,created_at.desc

[pppdns]

In Typescript, you can do something like this:

let query = supabase().from('your_table);

// Apply ordering as chained .order calls
for (const col of sortCriteria) {
  query = query.order(col);
}

const { data, error } = await query;