Login  |  Register
HTML5 Icon HTML5 Icon HTML5 Icon
TP on Social Media


Welcome, Guest. Please login or register.
Did you miss your activation email?

January 22, 2021, 09:06:07 AM

Login with username, password and session length
  • Total Posts: 191739
  • Total Topics: 20939
  • Online Today: 62
  • Online Ever: 1035
  • (November 26, 2020, 04:45:12 AM)
Users Online
Users: 1
Guests: 47
Total: 48

Author Topic: db_query error on 2.0.14 installation  (Read 9578 times)

0 Members and 2 Guests are viewing this topic.

Offline Arantor

  • Jr. Member
  • **
  • Posts: 11
Re: db_query error on 2.0.14 installation
« Reply #20 on: October 22, 2017, 03:57:17 AM »
Before we go any further, part of the problem is the assumption that GROUP BY has anything to do with PHP - it absolutely doesn't.

PHP 7 doesn't do anything related to GROUP BY. Neither does PHP 7.1. They don't change how the database expects to be communicated with, the only_group_by stuff is a change made by MySQL themselves and I'd assume you've upgraded from something like MySQL 5.5 to MySQL 5.7 where this is a newer ruling they added for strictness.

You will want to turn this setting off because other parts of SMF and other SMF mods still rely on it (it's something that has been tackled in SMF 2.1)

Tackling this particular code in TP is a little tricky as it involves rewriting the query in a really complicated way but I'll see if I have any ideas as the day goes on.

Offline lurkalot

  • Administrator
  • *
  • Posts: 7113
    • Camera Craniums
Re: db_query error on 2.0.14 installation
« Reply #21 on: October 22, 2017, 04:08:35 AM »
Thanks Arantor, that would be brilliant.  O0

I did wonder if it was a MySQL thing, after I googled the error. 

Offline coyoteboy

  • Jr. Member
  • **
  • Posts: 13
Re: db_query error on 2.0.14 installation
« Reply #22 on: October 22, 2017, 09:18:11 AM »
Yeah sorry folks, my very early morning brain screwed the two up. I need to sleep more.

You're right of course, it's not PHP at all.

I can turn off the setting, and I will, but I have other systems on this server that are expecting it (but not necessarily needing it).

Having read further into it (mysql isn't my thing) it looks like turning it off won't give any major issues and doesn't stop me doing what I need with my other systems. I'll disable it for now, but it would be nice to be up to current spec as it's not going to go away. I appreciate there may be other priorities though :)

Cheers folks