mirror of
https://github.com/frappe/erpnext.git
synced 2026-05-29 18:04:46 +00:00
mysql is generally smart enough to figure out which index is better
based on cardinality of index. While posting sort index is better for
low item high # of SLE scenario it's bad for high item variety each with
lower count of SLEs.
(cherry picked from commit 228e011819)
Co-authored-by: Ankush Menat <ankush@frappe.io>
This commit is contained in:
@@ -168,7 +168,7 @@ def get_stock_ledger_entries(filters, items):
|
|||||||
sle.company, sle.voucher_type, sle.qty_after_transaction, sle.stock_value_difference,
|
sle.company, sle.voucher_type, sle.qty_after_transaction, sle.stock_value_difference,
|
||||||
sle.item_code as name, sle.voucher_no, sle.stock_value, sle.batch_no
|
sle.item_code as name, sle.voucher_no, sle.stock_value, sle.batch_no
|
||||||
from
|
from
|
||||||
`tabStock Ledger Entry` sle force index (posting_sort_index)
|
`tabStock Ledger Entry` sle
|
||||||
where sle.docstatus < 2 %s %s
|
where sle.docstatus < 2 %s %s
|
||||||
and is_cancelled = 0
|
and is_cancelled = 0
|
||||||
order by sle.posting_date, sle.posting_time, sle.creation, sle.actual_qty""" % #nosec
|
order by sle.posting_date, sle.posting_time, sle.creation, sle.actual_qty""" % #nosec
|
||||||
|
|||||||
Reference in New Issue
Block a user