Thanks for your answer, but there is a point that is not totally correct . The bug appeared even when company_id was set to False on currency object… That means that user want to access currencies resources that where shared and do not belong to any company, so it appears to be a correct setup. That why that bug was so annoying.
But now we are at least aware of this potential cache glitch. I will try to take the orm patch and adapt it to have a more efficient filter done on Python size.
Hello,
Thanks for your answer, but there is a point that is not totally correct . The bug appeared even when company_id was set to False on currency object… That means that user want to access currencies resources that where shared and do not belong to any company, so it appears to be a correct setup. That why that bug was so annoying.
But now we are at least aware of this potential cache glitch. I will try to take the orm patch and adapt it to have a more efficient filter done on Python size.