Community: Framework mailing list archives

Computed field with inverse and store=false, field is saved anyway on the DB

Leonardo Donelli
- 02/11/2015 04:45:45
Hi guys,
Did anyone here implement a computed field with an inverse function
and store=False? I'm having a problem: when I edit the field in the
client, the field value is saved anyway in the database, even though

I also reported the problem on github, you can find more details here:

Does anyone have any idea of what might be happening and how to be
sure the computed field is never saved on the db?