I've logged this incident to MAMP Pro tow days back but no one yet back to me I was able to connect my PHP applications that was hosted on an older version of MAMP Pro version 4.1 (i guess) using the below shown connection setup *1Īfter upgrading to Mamp Pro 4.2, the PHP application failed to access MySQL 8Īt this point, MySQL 8 database was still working fine and accessible using Workbench 8,Īfter several unsuccessful attempts which include re-installation of Workbench 8, MySQL 8 and even MAMP Pro 4.2, I've reset the whole computer and carried out fresh installation of Workbench and MAMP Pro but the issue still persist and the PHP Application still can't access MySQL 8 ORDER BY mantis_bug_table.sticky DESC, il_priority ASC, mantis_bug_table.due_date DESC, mantis_bug_table.last_updated DESC, mantis_bug_table.date_submitted DESC.MySQL 8 which installed along with Workbench 8 was configured to work with port # 3307, as the port # 3306 was reserved by MAMP Pro for its own instance of MySQL ver 5.7 WHERE mantis_project_table.enabled =? AND (mantis_bug_table.project_id IN (?,?) OR mantis_bug_table.project_id IN (?,?) AND mantis_bug_table.view_state = ? OR mantis_bug_table.project_id IN (?,?) AND mantis_bug_table.reporter_id = ?)

SELECT TTB1.id, IP.itil_priority FROM mantis_bug_table TTB1 JOIN mantis_plugin_simpleITIL_incident_priority_table IP ON TTB1.id = IP.bug_id WHERE TTB1.project_id IN (1,17,28,44) GROUP BY TTB1.id ) SUBQ1 ON mantis_project_table.id = mantis_bug_table.project_id

SELECT DISTINCT mantis_bug_table.* FROM mantis_bug_table JOIN mantis_project_table Here the error Error received from database was 0003065: Expression 0000002 of ORDER BY clause is not in SELECT list, references column 'il_priority' which is not in SELECT list this is incompatible with DISTINCT for the query: I've done several searches on google and seems that depending on how each kind of DBMS choose to manage this situation throwing the error can be right.īecause I'm not an SQL expert I'm asking you to give a look to this situation in order to understand if change has to be done on this query in order to be sure, it will work as expected no matter the DBMS used.

This happens because MantisBT seems to extract data ONLY from mantis_bug_table. Then I face the error regarding the fact that a SELECT DISTINCT tries to order by a column not present on SELECT. OK also on my MAMP PRO installation that uses MySQL 5.6.38.Ī new QA environment on Windows was created using Bitnami WAMP 7.1.18 than installs: ĭoing tests with TimeTracking, an with my plugin gave OK, on my linux installation that uses MariaDB. I've used as a working model the TimeTracking plugin. I've been developing a plugin, and need to add a Column from an specific custom plugin table on bug view.

0024561: Sorting for Table Columns from a plugin Table Crashes on MySQL 5.7

Mamp pro windows mysql 5.6