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

Hello Jacques-Etienne,

Search on a selection field with '=' Operator it searches with Specified pattern.
Where as the ' ilike ' operator it searches related with that pattern.
So, It is ok with ' ilike ' if you use it instead of '=' operator.

Thanks.

The domain generated by the search view in the web client is wrong in the case of a selection field.
When I search records with state "draft", I want to search records where state = "draft" like with the GTK client. This will use the indexes in DB. (it cannot use indexes when you perform an "ilike" where query)

Anyway, the behavior is different with the GTK and web client. And it should be fixed in the web client.

Hello Jacques-Etienne,

Would you please elaborate with more information or proper example?
Because I have checked with stable-6 and Trunk code,
But it is working fine at my end.

Thanks.

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!

Hello Jacques-Etienne Baudoux (OpenERP),

Web client is also using '=' and index, for field.selection.
Then also, if you find any specific case (not possible because its generic) then please send us details.

Thanks.

You can reproduce the bug with this basic module:
lp:~jba-openerp/openobject-server/trunk-bug-715773

You'll see in the server log it generates:
[2011-02-21 20:16:23,112][?] DEBUG_RPC:params: 'bug715773.bug',
[2011-02-21 20:16:23,112][?] DEBUG_RPC:params: 'search',
[2011-02-21 20:16:23,112][?] DEBUG_RPC:params: [('state', 'ilike', 'draft')],

Hello Jacques-Etienne Baudoux (OpenERP),

The fix for web-client has been committed to lp:~openerp-dev/openobject-client-web/trunk-bug-715773-sma
with the following revision.
Revision-info:
4612 <email address hidden>

Soon it will be merged into trunk web-client.

Thank you for notifying.