I don't think there's a T-SQL statement for it. 
If you strongly need it, performance-wise, it's still best to 
distinct/groupby on the backend and randomize on the frontend (via python).

You can also randomize limitby parameters if you're feeling "random" at 
this level (limiting correctly with the count of total results, so 2 
queries needed in that case).


-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to