Closed (won't fix)
Project:
Image
Version:
4.7.x-1.x-dev
Component:
image.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Mar 2006 at 06:23 UTC
Updated:
16 Oct 2006 at 18:27 UTC
I couldn't get the "Latest image"-block working though the "Random image"-block worked fine. Putting the word changed in the query string in line 587 in single quotation marks ('changed') helped.
This problem may have occured because of the relatively new software my hoster provides (PHP 5.1.2, MySQL 4.1.15).
Comments
Comment #1
Standart commentedOk, this was too fast. Stupid, as my 'patch' seems to only deactivate the
ORDER BYstatement in some way in drupal. I played around with the SQL and found out that the following combinations work, respectively don't work:work (more than 1 result):
don't work (0 results - no error):
So the combination of
WHERE type='image'andORDER BYseems to be the problem. This appears to me to be a very special MySQL problem. Maybe someone has an idea how to explain this behaviour.Comment #2
benshell commentedInteresting... all five of your queries work and return more than one result on MySQL 4.1.18. Have you had a chance to try these queries on a different MySQL install? If you don't have access to another host, could you download and install MySQL on your workstation?
Comment #3
robo_arnold commentedI conducted the same tests on my local PC (Win XP Pro) running off MySQL 4.1.7 and observed exactly the same behavior as Standart. Weird.
Comment #4
Standart commentedSo obviously this is not a drupal (or image) bug. I can't believe such a simple query is not working in MySQL 4.1 prior to 4.1.18. I moved my site to a server running MySQL 5 now and of course it's working fine.
Comment #5
qube commentedI can confirm this issue on MySQL 4.1.11 on Debian.
MySQL 5.0.24 is working without this problem.
(Drupal 4.7.3, newest image and img_assist)