跳至內容
此問題已被標幟
5 回覆
116591 瀏覽次數
頭像
Atchuthan - Technical Consultant, Sodexis Inc

In what scenarios would we need to use '=ilike' in domain operation.

When we create a domain, we have multiple operators available in OpenERP 7 at server/openerp/osv/expression.py

TERM_OPERATORS = ('=', '!=', '<=', '<', '>', '>=', '=?', '=like', '=ilike', 'like', 'not like', 'ilike', 'not ilike', 'in', 'not in',  'child_of')

Can anyone provide me a scenario where we need to use these operators in domain:

1. =?
2. =like
3. =ilike
4. like
5. ilike
6. child_of

 

頭像
捨棄
頭像
René Schuster
最佳答案

As prakash says: The i is for case insensitive. While the "= prefix" searches for exact matching. Without the "= prefix", the orm will add % wildcards arround your search term.

Examples:

[('name', 'like', 'dog')]

This will find recods with name 'dog', 'dogs', 'bulldog', ... but not 'Dog'.

[('name', '=like', 'dog')]

This will find records with name 'dog' (it's almost exactly like the '=' operator).

[('name', 'ilike', 'dog')]

This is the most universal search. It will find records with name 'dog', 'DOGS', 'Bulldog', etc..

['name', '=ilike', 'dog')]

This will find records with name 'dog', 'DOG', 'Dog', 'DOg', DoG', 'dOG', 'doG' and 'dOg'.

They use '=ilike' in your crm/wizard example to match the email case insensitively, so that any capital letter is ignored in the search, since some mail clients allow capitol letters in email addresses, while others doesn't, I think.

 

Honestly, I have never seen or used the '=?' operator...

 

I think 'child_of' is somethink like an iterative search for child-relations:

[('parent_id', 'child_of', root_id)]

This will list all children and their children ... and so on for the root_id.

 

Regards.

頭像
捨棄
頭像
Guillaume Pothier
最佳答案

The difference between like/ilike and =like/=ilike is that with like/ilike, Odoo automatically appends and prepends a '%' to the search string before passing it to the database. So [('name', 'like', 'dog')] is equivalent to [('name', '=like', '%dog%')]. So you could use =like if you need to find the search string at the only beginning of the column, for instance [('name', '=like', 'dog%')]

頭像
捨棄
頭像
Audrius
最佳答案

'=?' operator makes the term TRUE if right statement is None or False otherwise behaves like '='

Reference:

openerp/osv/expression.py:1169

if right is False or right is None: 

# '=?' is a short-circuit that makes the term TRUE if right is None or False 

query = 'TRUE'

params = [] 

else: 

# '=?' behaves like '=' in other cases 

query, params = self.__leaf_to_sql( create_substitution_leaf(eleaf, (left, '=', right), model))

Sample: openerp/addons/base/tests/test_expression.py:120

user_ids = users_obj.search(cr, uid, [('name', 'like', 'test'), ('parent_id', '=?', False)]) 

self.assertEqual(set(user_ids), set([a, b1, b2]), '(x =? False) failed')

As it is shown in example, parent_id cannot be False if value doesn't exist: '=?' returns True or parent_id value

頭像
捨棄
頭像
Prakash
最佳答案

ILIKE keyword in PostgreSQL provides case insensitive search.

Reference:-  http://solaimurugan.blogspot.in/2010/07/ilike-operator-in-postgresql.html

頭像
捨棄
Atchuthan - Technical Consultant, Sodexis Inc
作者

so in cases why would we use =ilike?? In CRM/wizard/crm_lead_to_opportunity.py(line no:68) ids = lead_obj.search(cr, uid, [('email_from', '=ilike', email[0]), ('state', '!=', 'done')])

Prakash

please see the link http://stackoverflow.com/questions/4752705/case-insensitive-searches-queries based on the link examples need to use 'ilike'. But in the openerp Lead example it check only single record we can also use '=' instead of 'ilike'. Example:- [('email_from', '=', email[0]), ('state', '!=', 'done')]

頭像
Gerard ONeill
最佳答案

Normal odoo 'like' (and 'ilike' for the case insensitive version) allows the use of '%' and '_' within the search parameter.  It uses the SQL 'like' under the hood, which requires '%'s to either side to create the 'contains' operator, as other answers have mentioned.

So '=like' simply does not add those '%'s to either side when converting the operator to SQL.

An easy use case is the "Starts with" search:  ['field', '=like', 'Warren%'].

And the 'Ends with' search: ['field', '=like', '%hat']

And of course the exact search for a phrase with a beginning and an end: ['field', '=ilike', 'My % bag.']

Presumably early Odoo didn't think about the 'Starts With' and 'Ends With' cases.  So 'like', while being very close to its SQL counterpart, was changed in that interpretation of 'like' as 'contains'.  Probably soon afterwards, it was easy enough to remove the 'contains' functionality by adding = to the operator.  This was probably to evoke 'exactly like'  vibes.  If they wanted to evoke a more regex vibe, they should have used '^like$', which makes use of the two anchors from POSIX/Perl(PCRE) regex syntax.  Its ironic that Odoo is built on top of a Postgres DB which supports the 'similar to' operator which is *Very* 'regex like'.

頭像
捨棄