Project:
View Revisions: Issue #30526 | [ All Revisions ] [ Back to Issue ] | ||
Summary | 0030526: potential unneeded storage detail updates on changes for movement lines | ||
Revision | 2015-08-07 17:21 by alostale | ||
Steps To Reproduce | Seen in a customer instance with big volumes and high concurrency using picking module, logs show many times this query: update M_MovementLine set Updated=$1, EM_OBWPL_Itemstatus=$2, EM_OBWPL_Pickedqty=$3 where M_MovementLine_ID=$4 it is usually fast but sometimes becomes slow because it needs to update M_STORAGE_DETAIL which can be locked. Would it be necessary at all to call M_UPDATE_INVENTORY in this case? |
||
Revision | 2015-08-07 17:19 by alostale | ||
Steps To Reproduce | Seen in a customer instance with big volumes and high concurrency using picking module, logs show many times this query: update M_MovementLine set Updated=$1, EM_OBWPL_Itemstatus=$2, EM_OBWPL_Pickedqty=$3 where M_MovementLine_ID=$4 it is usually fast but sometimes becomes slow because it needs to update M_STORAGE_DETAIL which can be locked. Would be necessary at all to do the update in this case? |
Copyright © 2000 - 2009 MantisBT Group |