Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
erp5 erp5
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 136
    • Merge requests 136
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !1723

Merged
Created Jan 12, 2023 by Xiaowu Zhang@xiaowu.zhangDeveloper

fix data inconsistency after change preference

  • Overview 4
  • Commits 3
  • Changes 5

in erp5, preference datas are cached in erp5_ui_long cache factory, after change preference, those cached datas are cleared by preference_interaction_workflow

but in some scipts such as Resource_getIndividualVariationBaseCategoryItemList , Resource_getOptionalVariationBaseCategoryItemList...

we use also a cache on the top of preference data which make those scripts return inconsistent data after change preference

it more like that those scripts use cache in a bad way thus fix should be done on those scripts

Edited Jan 13, 2023 by Xiaowu Zhang
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fix_data_consistency
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7