Martin Trigaux 437116f3c4 [FIX] orm: custom m2m with different label ... At rev 84e9a67cdf a check to avoid the creation of ir.model.relation for custom modules was added. The condition is not correct as based on the string instead of the field name. We do not have access to column name at this level but the the m2m relation table do start with x_ for custom fields (see __init__ method).		2014-07-11 11:39:32 +02:00
..
__init__.py	API docs: settings file and titles at modules	2011-06-23 12:03:57 +03:00
expression.py	Server Translation: Fixed the issue search on translated field do not return true result, search on tranlsated field fails due to expression parsing which fetches ids from ir_translation as well as working table and UNION of this makes search fruitless, also search fails for in language other then english when you enter part of a string for the field to search.	2014-06-24 17:42:48 +05:30
fields.py	[FIX] fields property: do not create empty properties	2014-06-25 10:57:10 +02:00
orm.py	[FIX] orm: custom m2m with different label	2014-07-11 11:39:32 +02:00
osv.py	[IMP] osv: display full traceback in terminal (not client side) when a check fails instead of minimal error	2014-01-08 15:05:54 +01:00
query.py	[REM] unnecessary parens	2012-12-14 13:38:03 +01:00