Mihir Kandoi 0b4e52e8d7 fix(buying): make Purchase Order Analysis GROUP BY Postgres-valid ...

get_data() grouped only by Purchase Order Item while selecting Purchase
Order parent columns. MariaDB allows this loose GROUP BY; Postgres rejects
it with "column ... must appear in the GROUP BY clause".

Add the Purchase Order PK (po.name) to the GROUP BY. po.name is 1:1 with
the already-grouped po_item.name, so groups are unchanged and the result
is identical on MariaDB.

Adds a test (no test file existed) that runs the report and asserts the PO
is listed, exercising the GROUP BY on both engines.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-21 04:40:35 +05:30

..

__init__.py

feat: Buying Desk, Dashboard and Reports

2020-05-05 23:58:08 +05:30

purchase_order_analysis.js

fix: autofixes by semgrep

2026-01-01 21:56:12 +05:30

purchase_order_analysis.json

fix: Fixed Dashboard Charts, modified fixtures and minor changes

2020-05-15 23:37:48 +05:30

purchase_order_analysis.py

fix(buying): make Purchase Order Analysis GROUP BY Postgres-valid

2026-06-21 04:40:35 +05:30

test_purchase_order_analysis.py

fix(buying): make Purchase Order Analysis GROUP BY Postgres-valid

2026-06-21 04:40:35 +05:30