New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable selective cache invalidation #5183
Comments
metas-ts
added a commit
that referenced
this issue
May 9, 2019
Dev-Test👍 I set a breakpoint in the |
metas-ts
added a commit
that referenced
this issue
May 13, 2019
* [#5101](#5101) Area search - Geocoding * [#5175](#5175) Add language parameter to SQL Function PP_Product_BOM_Recursive * [#5177](#5177) Checking BtM and PZN with Modulo 11 * [#5183](#5183) Enable selective cache invalidation * [#78](metasfresh/metasfresh-e2e-legacy#78) Enable checking for user notifications * [#5172](#5172) Pricing Conditions Report Error * [#5182](#5182) forum-datenaustausch.ch XML externalId not sufficiently unique * [#5185](#5185) forum-datenaustausch.ch XML pre-existing documents are removed from XML on exporting * [#5186](#5186) Invoice candidate from order line candidate - pricelist precision not applied when computing PriceActual * [#1189](metasfresh/metasfresh-webui-api-legacy#1189) Results missing in batch entry dropdown * [#1194](metasfresh/metasfresh-webui-api-legacy#1194) Non-Mandatory BigDecimal fields inititalized with 0 * [#79](metasfresh/metasfresh-e2e-legacy#79) Fix sales order test metasfresh/me03#1680
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a bug or feature request?
FR; triggered by and intended to first help with #5162
What is the current behavior?
for each given TableRecordReference, the whole CCache is reset.
What is the expected or desired behavior?
There shall be means for a dev to make it so only the cache entries that need invalidating (i.e. that need to be recomputed) are invalidated
The text was updated successfully, but these errors were encountered: