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
{{ message }}
This repository has been archived by the owner on Nov 24, 2023. It is now read-only.
The problem with the old sql statement is that the elements of the array abilities could be in a jumbled or in any order.
Also the array of levels. by ability levels could also be jumbled or in any order.
In the new query, they would be sorted in ascending order by ability id and ability level respectively.
Changes
# before
WHERE t4.id = 5
# after
WHERE t4.id = 5
ORDER BY ability_table."abilityId" ASC;
# before
ARRAY_AGG (ability_level.cost) "levelCosts"
# after
ARRAY_AGG (ability_level.cost ORDER BY ability_level.level) "levelCosts"
The problem with the old sql statement is that the elements of the array abilities could be in a jumbled or in any order.
Also the array of levels. by ability levels could also be jumbled or in any order.
In the new query, they would be sorted in ascending order by ability id and ability level respectively.
Changes
This is the wrong (old) query
This is the correct (new) query
The text was updated successfully, but these errors were encountered: