framework must not accept xml-rpc to write into function fields

Bug #1073302 reported by Ferdinand
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Confirmed
Medium
OpenERP's Framework R&D

Bug Description

6.1 this statement "works"

reason: if a field becomes a stored function field (during upgrade, module install ...) - any remote "already working" application writing values using xml-rpc will continue to write and succeed without notification that the values are NOT written any more, because the function fields gets updated and stored with the correct value.

after executing this statement the value of complete_name = "New CRM" even though the application has written "100".

***************************** Test case ************************
import xmlrpclib

username = 'demo' #the user
pwd = 'demo' #the password of the user
dbname = 'demo' #the database

# Get the uid
sock_common = xmlrpclib.ServerProxy ('http://localhost:8069/xmlrpc/common')
uid = sock_common.login(dbname, username, pwd)

#replace localhost with the address of the server
sock = xmlrpclib.ServerProxy('http://localhost:8069/xmlrpc/object')

crm = {
   'name': 'New CRM',
   'complete_name' : 100,
}

crm_id = sock.execute(dbname, uid, pwd, 'crm.case.section', 'create', crm)

print crm_id
******************************

description: updated
Changed in openobject-server:
assignee: nobody → OpenERP's Framework R&D (openerp-dev-framework)
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.