c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <715773@xxxxxxxxxxxxxxxxxx>]

Indeed, the search operator that the web client must use when sending
search to the server is '=', because the values of the selection are
fixed. The GTK client does this properly.

Thanks for reporting!

** Changed in: openobject-client-web
   Importance: Undecided => Low

** Changed in: openobject-client-web
       Status: Incomplete => Confirmed

** Changed in: openobject-client-web
    Milestone: None => 6.0.2

** Changed in: openobject-client-web
     Assignee: (unassigned) => OpenERP SA's Web Client R&D (openerp-dev-web)

** Summary changed:

- [6.0] search on selection fields - ilike and index
+ [6.0] web client should use exact match search (=) for searching on fields.selection

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/715773

Title:
  [6.0] web client should use exact match search (=) for searching on
  fields.selection

Status in OpenERP Web Client:
  Confirmed

Bug description:
  When you perform a search on a selection field in the web client, the generated expression doesn't use the correct operator "=" but "ilike"
  it should be:
  [('state', '=', 'draft')]
  instead of
  [('state', 'ilike', 'draft')]

  First it is not correct and secondly, it's breaking the use of the
  indexes.