You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
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
Additional context
The same issue was reported in Discord in December, but no GitHub issue was created.
The text was updated successfully, but these errors were encountered: