tree d999a5c4769c686ad5b1059740fed703aa615e3f
parent 6acdb2f00b8437abc43d6ca2b92b33d629c5c764
author Ankush Menat <ankush@frappe.io> 1639576121 +0530
committer GitHub <noreply@github.com> 1639576121 +0530
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhufI5CRBK7hj4Ov3rIwAAA/MIAHFXFhxEefexCwjI49v+otZj
 qci28mHgrysa/nz9IeXYS6o8t7ExIEHhugCl0BsfrE1AYHPOzD46BcaQ7EMy2kuT
 kvPOFF8S78NGbF01FruLRu2+ZkQ2tZZEgnO6u3oQ/OH9Opje41CsiRS6FZtsviju
 h3Sppx7GviYCfN7mcY7bmMVQjTR7M/2AMc1n270+jj8nla1dEzmu6dNeHSiuCQor
 MjTlt3DJRFDDfpOGalZRqfdhNvYYBxDx6Jdf8xxsMguELuVFVJYh7+ZCYGA7zdRg
 +gx7Z4JABKcSpkat1ZNFrSLbB/Nkigb4FbfQ0cZj3DM5ny9f4z8tlQjIVn9PfGw=
 =hPK3
 -----END PGP SIGNATURE-----
 

perf: remove forcing of posting sort index on stock balance (#28902)

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.