Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Cannot Reproduce
-
29.1.3, 30.0.2
-
None
-
CP: sprint 91
-
1
-
Core: Platform
Description
See MODORDERSTOR-158 for details. RMB up to 29.1.2 is known to work. RMB 29.1.3 introduced RMB-498 "Truncate b-tree string for 2712 index row size".
Minimal reproducer:
GET /orders-storage/orders?query=id=* sortBy dateOrdered/sort.descending
This causes
SELECT DISTINCT ON expressions must match initial ORDER BY expressions
SELECT COUNT(*) FROM (
SELECT DISTINCT ON( left(lower(f_unaccent(orders_view.metadata->>'dateOrdered')),600) ,
lower(f_unaccent(metadata->>'poNumber'))) jsonb
FROM diku_mod_orders_storage.orders_view
WHERE true
ORDER BY left(lower(f_unaccent(orders_view.metadata->>'dateOrdered')),600) DESC,
lower(f_unaccent(orders_view.metadata->>'dateOrdered')) DESC
LIMIT 1000) x
Adding the second ORDER BY element fixes it:
SELECT DISTINCT ON expressions must match initial ORDER BY expressions
SELECT COUNT(*) FROM (
SELECT DISTINCT ON( left(lower(f_unaccent(orders_view.metadata->>'dateOrdered')),600) ,
lower(f_unaccent(orders_view.metadata->>'dateOrdered')),
lower(f_unaccent(metadata->>'poNumber'))) jsonb
FROM diku_mod_orders_storage.orders_view
WHERE true
ORDER BY left(lower(f_unaccent(orders_view.metadata->>'dateOrdered')),600) DESC,
lower(f_unaccent(orders_view.metadata->>'dateOrdered')) DESC
LIMIT 1000) x
The bug only affects descending sort, sorting ascending works:
GET /orders-storage/orders?query=id=* sortBy dateOrdered
TestRail: Results
Attachments
Issue Links
- blocks
-
-
- Closed
-
- relates to
-
-
- Closed
-