-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
[ADD] event_kanban_view_optimized #62
Conversation
<field name="priority" eval="99999"/> | ||
<field name="arch" type="xml"> | ||
<field name="is_subscribed" position="replace"/> | ||
<div groups="base.group_user,base.group_portal" position="replace"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this replace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the section where is_subscribed
variable is used: https://github.com/odoo/odoo/blob/4809b572835a94543cd1f37e621a98fabec053fd/addons/event/event_view.xml#L227
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested in production environment of a customers as in runbot there is not such an amount of events an registries.
Event kanban view optimized | ||
=========================== | ||
|
||
Event kanban view computes ``is_subscribed`` field per each event and loading time |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"per event" or "for each event"
Event kanban view optimized
Event kanban view computes
is_subscribed
field per each event and loading timeis degraded when events have many registrations. This addon removes this field
from kanban view in order to optimize loading time.
@Tecnativa