Usually, this is a MySQL issue. 5.0.51 is notorious for this.
It’s not the best solution, but I fixed it on one site by removing the GROUP BY clause in the Wayfinder code.
I wonder if one can check the mySQL version from php and fire an alternate sql statement when in 5.051?
A thing of beauty is a joy forever ( John Keats)
Quote from: brandan at Jul 20, 2008, 10:15 AM
thanks bobray. a bit of research turned up some confirmation that this is indeed a mysql issue and that there is a patch available. unfortunately it won’t be committed in the community server until 5.0.52 is released.
http://bugs.mysql.com/bug.php?id=32202
I hope that happens in my lifetime.
That bug (and 5.0.51) have been around for ages.
-
MODX Staff
- 10,725 Posts
I think Sun has ruined our favorite open source database (big surprise eh?). Since 5.0.58 has been release in Enterprise for quite some time now, you have to assume they are delaying these fixes on purpose to encourage the purchasing of licenses... sigh...
-
☆ A M B ☆
- 24,524 Posts
Yeah, I’ve been casually cruising through the Manager scripts looking for hard-coded mysql calls with the thought of getting that cleaned up once and for all, then it would be a piece of cake to just create a new db class file for postgres, or any other database. I’ve kind of had sqlite in mind for a while now. Would be great for uber-cheap hosting with no database, but php5.
-
☆ A M B ☆
- 24,524 Posts
No, I’ve got enough on my mind without trying to figure out svn too. I’ll just give it to you guys to do with whatever you want. I’ll provide a changelog along with the files. But don’t hold your breath.