sort by random broken

I have applied this fix to my sites, and it seems to be working.

However I do not know it this will break pgsql again.

Tested this on PostgreSQL in 4.7 and all is good. RTBC as far as PostgreSQL is concerned.

--
Sammy Spets
Synerger
http://synerger.com

I've applied this patch and its working fine with PostgreSQL 8.1.4 and Drupal 5.0 beta 2. The only thing that tripped me up was forgetting to edit and re-save the view using random to get it to re-generate the query sans '()'.

I applied what I think is a better patch. I believe this works in all circumstances, but time will tell! Anyone using PGSQL, I invite you to try out HEAD and see if it works.

Ok the proper fix should be backported from 5 in the 4.7.x-1.x-dev branch.

Argh I left out the bit that gives the random sort an alias. Sigh.

Since this has only been 3 hours I redid the release to include the missing alias. (It's been in the drupal 5 version for days but I'm apparently getting worse and worse with branch management =)

If you downloaded Views 4.7.x-1.2 between 10am and 1pm pacific time today, download it again.

I'm still having this problem. I patched my views_query.inc and couldn't get it to work...

this is the error:

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '() FROM node node LEFT JOIN term_node term_node ON node.nid = term_node.nid WHE' at line 1 query: SELECT node.nid, rand() AS _rand() FROM node node LEFT JOIN term_node term_node ON node.nid = term_node.nid WHERE (node.status = '1') AND (node.type IN ('image')) AND (term_node.tid IN ('8')) ORDER BY _rand() ASC LIMIT 0, 1 in

I've also attached the views_query.inc im using...

thanks

s

Hello,

I'm transferring a drupal SQL database between two different hosts (and
hosting companies) via a backup and restore sequence.

The old host WB-hosting runs MySQL version 5.0.24-standard
while the KB says that site5.com runs sql v 4.1.21

and I'm getting an error I believe relates to the different SQL versions,
but it gives an error that is similar to one cited in this thread.

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '() FROM node node LEFT JOIN node_revisions node_revisions ON node.vid = node_re' at line 1 query: SELECT DISTINCT(node.nid), rand() AS _rand() FROM node node LEFT JOIN node_revisions node_revisions ON node.vid = node_revisions.vid WHERE (node.type IN ('forum')) AND (UPPER(node_revisions.body) LIKE UPPER('%Thank%')) ORDER BY _rand() ASC LIMIT 0, 1 in /home/kettleb/public_html/KS88/includes/database.mysql.inc on line 120.

Let me know if there is any more info that would be useful.

Thank you,

according to last two reports not fixed.

Here is my query output, using "views_query.inc,v 1.48.2.12 2007/01/16 04:21:55"
SELECT node.nid, rand(), node.title AS node_title, node.changed AS node_changed, node_data_field_salary_sought.field_salary_sought_value AS node_data_field_salary_sought_field_salary_sought_value, node_data_field_current_location.field_current_location_value AS node_data_field_current_location_field_current_location_value FROM node node LEFT JOIN node_data_field_salary_sought node_data_field_salary_sought ON node.vid = node_data_field_salary_sought.vid LEFT JOIN node_data_field_current_location node_data_field_current_location ON node.vid = node_data_field_current_location.vid WHERE (node.status = '1') AND (node.type IN ('content_job_listing_entry')) ORDER BY ASC LIMIT 0, 5

Fiddling a bit with the views solved the weird bug. I removed and added the view entirely. Seems some combination of a broken view and a stale cache.

Can strooltz and dkashen please confirm that removing + re-adding the view solves their Database error too?

setting this to 'needs more info'

I was going to ask if you had resaved the view; the view you exported is cachable, and Views currently caches the query on the view. (Yes, this has been creating alarming side effects, but I was concerned about caching it in the cache tables. Clearly I should have, and in the future I will.

merely re-saving did not help. I really had to remove the old one entirely and add a new one (by hand).