xmlrpc interface: inconsistent default arguments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Confirmed
|
Wishlist
|
OpenERP's Framework R&D |
Bug Description
for overloaded orm methods, default arguments are varying which make some basic xmlrpc calls to fail for some objects and succeed for others.
For instance, "name_search" is declared in orm.py as:
/
| name_search(self, cr, user, name='', args=None, operator='ilike', context=None, limit=100):
\
so basically:
/
| OBJ.xmlrpclib.
| OBJ.execute(
\
should work for any object name (NAME) in the system, unfortunately, it's not, as some overloaded name_search method don't set all the default values (e.g. 3rd arg name).
Some other calls are also probably affected. This is not a critical issue, but the behavior should be consistent (either _no_ defaults or same defaults everywhere).
Changed in openobject-server: | |
assignee: | nobody → OpenERP's Framework R&D (openerp-dev-framework) |
importance: | Undecided → Low |
status: | Incomplete → Confirmed |
Hello,
Could you elaborate on this and perhaps give the name of the classes that you found have a name_search with incorrect parameter defaults? Is that in server or in the addons?
Many thanks!