Commit 16463935 authored by Vincent Pelletier's avatar Vincent Pelletier

Remove this log, it is (currently) wrong.

 - providing pre-mapped column to catalog is the only way to make a mapping explicit when mapping fails because of ambiguous choice
   -> it must not be discouraged
 - having in catalog configuration pre-mapped columns (sql_search_result_keys) is currently unavoidable
   -> it must not trigger a warning


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@25885 20353a03-c40f-0410-a6d1-a30d3c3de9de
parent a0b641bd
...@@ -106,7 +106,6 @@ class ColumnMap(object): ...@@ -106,7 +106,6 @@ class ColumnMap(object):
if '.' in column: if '.' in column:
# Assuming the part before the dot is a real table name, not an alias. # Assuming the part before the dot is a real table name, not an alias.
table, column = column.split('.') table, column = column.split('.')
LOG('ColumnMap', 100, 'Column %r is pre-mapped. This use is strongly discouraged.' % (raw_column, ))
else: else:
table = None table = None
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment