You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The feature allowing to batch single line updates in stored procedures was removed due to a correctness issue. That significantly impacted the NewOrder operation where this feature was used.
We still can take advantage of batching: there is no correctness issue if single line updates are inside CTEs. Hence we should wrap the update statements into CTEs.
The text was updated successfully, but these errors were encountered:
* [#125] Use CTEs in the updatestock procedures
* [#125] Use CTEs in geopartitioned schema manager
* Removing no null from column definitions.
* setting yb_enable_expression_pushdown at connection level
Co-authored-by: Hemant Bhanawat <hbhanawat@yugabyte.com>
Co-authored-by: Andrei Martsinchyk <amartsinchyk@yugabyte.com>
The feature allowing to batch single line updates in stored procedures was removed due to a correctness issue. That significantly impacted the NewOrder operation where this feature was used.
We still can take advantage of batching: there is no correctness issue if single line updates are inside CTEs. Hence we should wrap the update statements into CTEs.
The text was updated successfully, but these errors were encountered: