Mysql error with mysql 5.7.14

[Portugao]

Q	A
Zikula Version	1.5.dev
PHP Version	5.6.25
Mysql	5.7.14

Expected behavior

Successful call of modules overview in backend

Actual behavior

An exception occurred while executing 'SELECT DISTINCT id_0 FROM (SELECT m0_.id AS id_0, m0_.name AS name_1, m0_.type AS type_2, m0_.displayname AS displayname_3, m0_.url AS url_4, m0_.description AS description_5, m0_.directory AS directory_6, m0_.version AS version_7, m0_.capabilities AS capabilities_8, m0_.state AS state_9, m0_.securityschema AS securityschema_10, m0_.core_min AS core_min_11, m0_.core_max AS core_max_12 FROM modules m0_) dctrn_result ORDER BY displayname_3 ASC LIMIT 40 OFFSET 0': SQLSTATE[HY000]: General error: 3065 Expression #1 of ORDER BY clause is not in SELECT list, references column 'dctrn_result.displayname_3' which is not in SELECT list; this is incompatible with DISTINCT

SQLSTATE[HY000]: General error: 3065 Expression #1 of ORDER BY clause is not in SELECT list, references column 'dctrn_result.displayname_3' which is not in SELECT list; this is incompatible with DISTINCT

Steps to reproduce

Try to call the modules list in admin area.

See:
laravel-doctrine/orm#264

[Portugao]

Setting sql-mode="" on local wamp server solves this problem.
So I don't know if it is really an issue?!

[Guite]

See #2852

[Portugao]

Hmmhmm...
Long time since this is known.

[Guite]

Actually it is fixed already in doctrine/orm#6143

But Doctrine ORM 2.6.0 is not finished, thus the fix is not included in Zikula yet.
It looks like it is almost completed though: https://github.com/doctrine/doctrine2/milestone/2

Closing as NOT CORE.