Skip to content
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.

Sign up for GitHub

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

Jump to bottom

support registry database signaling to #40

Open
sbidoul opened this issue May 6, 2021 · 0 comments · May be fixed by #41
Open

support registry database signaling to #40

sbidoul opened this issue May 6, 2021 · 0 comments · May be fixed by #41
Labels
enhancement New feature or request

Comments

@sbidoul
Copy link
Member

sbidoul commented May 6, 2021

Currently, when a click-odoo script makes change that require a registry reload or cache invalidation, the information is not propagated to other Odoo instances running concurrently on the same database.

Conversely, if an Odoo instance running on the same database as a long running click-odoo script that does several transactions will not receive information that the registry needs reloading.
@sbidoul sbidoul added the enhancement New feature or request label May 6, 2021
@sbidoul sbidoul linked a pull request May 6, 2021 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement registry change signaling acsone/click-odoo
1 participant
@sbidoul