The error message you're encountering is related to the ONLY_FULL_GROUP_BY SQL mode in MySQL. This mode is enabled by default in recent versions of MySQL and enforces strict rules for the GROUP BY clause to ensure that the result set is deterministic. When you get this error, it means that the SELECT statement contains columns that are not part of the GROUP BY clause and are not part of an aggregate function (like SUM, COUNT, etc.).

To resolve this issue, you have a few options:

Include Non-aggregated Columns in the GROUP BY Clause:
You can modify your query to include all non-aggregated columns in the GROUP BY clause. This makes the query more explicit and ensures that the result is deterministic.

Example:
```
SELECT column1, column2, SUM(column3)
FROM your_table
GROUP BY column1, column2;
```
Use Aggregate Functions for Non-grouped Columns:
If you don't want to include a column in the GROUP BY clause but you still want to include it in the result, you should use an aggregate function (e.g., SUM, MAX, MIN, AVG, etc.) to specify how to handle that column. This is useful when you want to retrieve aggregated data alongside non-aggregated data.

Example:
```
SELECT column1, MAX(column2), SUM(column3)
FROM your_table
GROUP BY column1;
```
Disable ONLY_FULL_GROUP_BY Mode:
If your SQL query is complex and you want to use non-standard SQL behavior, you can disable the ONLY_FULL_GROUP_BY SQL mode. However, be cautious with this approach, as it can lead to ambiguous or unexpected results.

You can disable it for your session with the following SQL command:
```
SET sql_mode=(SELECT REPLACE(@@sql_mode,'ONLY_FULL_GROUP_BY',''));
```
Make sure you understand the consequences of disabling this mode in your specific use case.

Before making any changes, it's essential to understand the data you're working with and the specific requirements of your query. Be careful when using option 3 (disabling ONLY_FULL_GROUP_BY) as it can lead to unexpected results if used improperly. It's generally recommended to use options 1 and 2 to write more precise and understandable SQL queries that follow the standards.

SQL Showing error #1055