I noticed that it is used in `hr.employee.public`:
```
image_128 = fields.Image("Image 128", compute='_compute_image', compute_sudo=True)
def _compute_image(self):
for employee in self:
employee_id = self.sudo().env['hr.employee'].browse(employee.id)
...
```
in the compute method sudo() is used anyways, which implies that compute_sudo doesn't change the self in the compute method to be equivalent to self.sudo();
Then what is the point in adding `compute_sudo`?
Compute sudo is described in the docs as "whether the field should be recomputed as superuser
to bypass access rights (by default True for stored fields, False
for non stored fields)"
but what does it mean? the user in the method is not the superuser unless sudo() is explicitly used.
As sudo bypasses access rights ,in compute_sudo compute field while computing itself again it will not look for the users access rights and compute it as its for superuser.
Create an account today to enjoy exclusive features and engage with our awesome community!
Prijavi| Related Posts | Odgovori | Prikazi | Aktivnost | |
|---|---|---|---|---|
|
compute issue
Solved
|
|
1
maj 21
|
5549 | |
|
2
maj 25
|
2853 | ||
|
2
avg. 22
|
7456 | ||
|
2
jul. 22
|
9409 | ||
|
1
dec. 20
|
40966 |
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
