Since the recent relase of python-sql I’ve seen two of our tryton tests suites failing with the following exception:
ERROR: test_ir_action_window (tests.test_xxxx.xxxxTestCase)
Test action windows are correctly defined
----------------------------------------------------------------------
Traceback (most recent call last):
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/trytond/tests/test_tryton.py", line 203, in wrapper
result = func(*args, **kwargs)
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/trytond/tests/test_tryton.py", line 615, in test_ir_action_window
domain, order=order, limit=action_window.limit)
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/trytond/model/modelsql.py", line 1313, in search
cursor.execute(*select)
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/sql/__init__.py", line 204, in __iter__
yield self.params
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/sql/__init__.py", line 649, in params
p.extend(self.from_.params)
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/sql/__init__.py", line 1121, in params
p.extend(from_.params)
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/sql/__init__.py", line 649, in params
p.extend(self.from_.params)
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/sql/__init__.py", line 1121, in params
p.extend(from_.params)
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/sql/__init__.py", line 1066, in params
if hasattr(item, 'params'):
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/sql/__init__.py", line 1066, in params
if hasattr(item, 'params'):
File "/builds/kopen/xxxx/.tox/py35-postgresql/lib/python3.5/site-packages/sql/__init__.py", line 1067, in params
p.extend(item.params)
TypeError: 'Column' object is not iterable
This is only raised when using postgresql backend, it works without any issue on sqlite backend.
We have not modified anything of our module, so this seems clearly reeelated to the new release.
Does anyone found any similar issues?
Any idea on who to fix it?