# MYSQL error after updating to version 5.7

**URL:** <https://www.dolibarr.org/forum/t/mysql-error-after-updating-to-version-5-7/30836>\
**Category:** Developing for Dolibarr\
**Created:** [December 10, 2025, 7:55am UTC](https://www.dolibarr.org/forum/t/mysql-error-after-updating-to-version-5-7/30836 "2025-12-10T07:55:15Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mgribaudo](https://www.dolibarr.org/forum/user_avatar/www.dolibarr.org/mgribaudo/32/3096_2.png) [@mgribaudo](https://www.dolibarr.org/forum/u/mgribaudo)\
**Post date:** [December 10, 2025, 7:55am UTC](https://www.dolibarr.org/forum/t/mysql-error-after-updating-to-version-5-7/30836/1 "2025-12-10T07:55:16Z")

</div>

Hi everyone,  
with my Dolibarr after updating MYSQL to version 5.7, the product list returns this error:

**Latest database access request error:** SELECT p.rowid, p.ref, p.ref\_ext, p.description, p.label, p.fk\_product\_type, p.barcode, p.price, p.tva\_tx, p.price\_ttc, p.price\_base\_type, p.entity, p.fk\_product\_type, p.duration, p.finished, p.tosell, p.tobuy, p.seuil\_stock\_alerte, p.desiredstock, p.tobatch, p.accountancy\_code\_sell, p.accountancy\_code\_sell\_intra, p.accountancy\_code\_sell\_export, p.accountancy\_code\_buy, p.accountancy\_code\_buy\_intra, p.accountancy\_code\_buy\_export, p.datec as date\_creation, p.tms as date\_modification, p.pmp, p.stock, p.cost\_price, p.weight, p.weight\_units, p.length, p.length\_units, p.width, p.width\_units, p.height, p.height\_units, p.surface, p.surface\_units, p.volume, p.volume\_units, p.fk\_country, p.fk\_state, p.import\_key, MIN(pfp.unitprice) as bestpurchaseprice FROM llx\_product as p LEFT JOIN llx\_product\_fournisseur\_price as pfp ON p.rowid = pfp.fk\_product WHERE p.entity IN (3) AND p.fk\_product\_type \<\> 1 GROUP BY p.rowid, p.ref, p.description, p.label, p.barcode, p.price, p.tva\_tx, p.price\_ttc, p.price\_base\_type, p.fk\_product\_type, p.duration, p.finished, p.tosell, p.tobuy, p.seuil\_stock\_alerte, p.desiredstock, p.datec, p.tms, p.entity, p.tobatch, p.pmp, p.cost\_price, p.stock, p.accountancy\_code\_sell, p.accountancy\_code\_sell\_intra, p.accountancy\_code\_sell\_export, p.accountancy\_code\_buy, p.accountancy\_code\_buy\_intra, p.accountancy\_code\_buy\_export, p.weight, p.weight\_units, p.length, p.length\_units, p.width, p.width\_units, p.height, p.height\_units, p.surface, p.surface\_units, p.volume, p.volume\_units, p.fk\_country, p.fk\_state, p.import\_key ORDER BY p.ref ASC LIMIT 26  
**Return code for latest database access request error:** DB\_ERROR\_1055  
**Information for latest database access request error:** Expression #3 of SELECT list is not in GROUP BY clause and contains nonaggregated column ‘Sql172321\_5.p.ref\_ext’ which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql\_mode=only\_full\_group\_by

A [web search](https://stackoverflow.com/questions/41887460/select-list-is-not-in-group-by-clause-and-contains-nonaggregated-column-inc) tells me to change the DB settings:

SET GLOBAL sql\_mode=(SELECT REPLACE(@@sql\_mode,‘ONLY\_FULL\_GROUP\_BY’,‘’));

My provider won’t let me (or won’t) change the settings.

What can I do?

---

<div class="post-metadata">

**Author:** ![saikatkoley](https://www.dolibarr.org/forum/user_avatar/www.dolibarr.org/saikatkoley/32/8716_2.png) [@saikatkoley](https://www.dolibarr.org/forum/u/saikatkoley)\
**Post date:** [December 10, 2025, 11:47am UTC](https://www.dolibarr.org/forum/t/mysql-error-after-updating-to-version-5-7/30836/2 "2025-12-10T11:47:02Z")

</div>

Hi @mgribaudo

If you don’t mind, which Dolibarr version are you using now? Have you tried the **ANY\_VALUE()?**

Or you can add **all non-aggregated fields** (like `p.ref_ext`) to the `GROUP BY` clause. Try once if not yet.

Thanks a& Regards  
Saikat Koley  
Software Developer(Dolibarr)  
Call/WhatsApp : +919903256573  
Email : [saikatkoley@hotmail.com](mailto:saikatkoley@hotmail.com)

[https://www.linkedin.com/in/saikatkoley/](https://www.linkedin.com/in/saikatkoley/)

---

<div class="post-metadata">

**Author:** ![mgribaudo](https://www.dolibarr.org/forum/user_avatar/www.dolibarr.org/mgribaudo/32/3096_2.png) [@mgribaudo](https://www.dolibarr.org/forum/u/mgribaudo)\
**Post date:** [December 10, 2025, 12:00pm UTC](https://www.dolibarr.org/forum/t/mysql-error-after-updating-to-version-5-7/30836/3 "2025-12-10T12:00:04Z")

</div>

Hi Saikat,  
Thanks for your reply.  
I’m using version 22.  
The problem, however, isn’t with one of my modules, but with the product list.

http:///xxxxxxxx/dolibarr/htdocs/product/list.php

---

<div class="post-metadata">

**Author:** ![saikatkoley](https://www.dolibarr.org/forum/user_avatar/www.dolibarr.org/saikatkoley/32/8716_2.png) [@saikatkoley](https://www.dolibarr.org/forum/u/saikatkoley)\
**Post date:** [December 10, 2025, 3:31pm UTC](https://www.dolibarr.org/forum/t/mysql-error-after-updating-to-version-5-7/30836/4 "2025-12-10T15:31:57Z")

</div>

@mgribaudo I can understand. I faced the same problem before but not in product list somewhere else I can’t remember now.

---

<div class="post-metadata">

**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\
**Post date:** [December 10, 2025, 5:09pm UTC](https://www.dolibarr.org/forum/t/mysql-error-after-updating-to-version-5-7/30836/5 "2025-12-10T17:09:33Z")

</div>

can you get a backup of your database? Store that somewhere safe, and then take a backup copy of the backup.

Work on the copy, safely store the backup.

You can run mariadb in a container that you can initialise from a mysqldump file.

Then run a dolibarr container talking to the mariadb.

Can you set a sql\_mode for each database, or only globally?

---

<div class="post-metadata">

**Author:** ![mgribaudo](https://www.dolibarr.org/forum/user_avatar/www.dolibarr.org/mgribaudo/32/3096_2.png) [@mgribaudo](https://www.dolibarr.org/forum/u/mgribaudo)\
**Post date:** [December 11, 2025, 6:43am UTC](https://www.dolibarr.org/forum/t/mysql-error-after-updating-to-version-5-7/30836/6 "2025-12-11T06:43:49Z")

</div>

Thanks @saikatkoley & @jonbendtsen  
I tried logging in today and… just as the error appeared, it disappeared today.  
Computer magic! 🙃

---

<div class="post-metadata">

**Author:** ![saikatkoley](https://www.dolibarr.org/forum/user_avatar/www.dolibarr.org/saikatkoley/32/8716_2.png) [@saikatkoley](https://www.dolibarr.org/forum/u/saikatkoley)\
**Post date:** [December 11, 2025, 3:30pm UTC](https://www.dolibarr.org/forum/t/mysql-error-after-updating-to-version-5-7/30836/7 "2025-12-11T15:30:24Z")

</div>

@mgribaudo great then 🙂
