With that said, if it's a factor of needing to do _other_ things in Rev at the same time, programming efficiency, etc- then it's a perfectly fine solution.
I would be shocked to find that Rev is better optimized for sorting than MySQL in any general sense. I'm wondering if it's worth pulling out any more specifics that someone can share about their table structures, queries, etc?
Please note I don't mean that sorting should literally be offloaded back to the database- but that there is almost always a fast way to get it that way in the first place, especially if we're just dealing with recID lookups and sorts.
- Brian
I've been heavily using Rev cgi and mySQL during the past few months, and I found out that extracting raw data from the db and processing them (sorting, comparing...) in Transcript is most of the time much faster than writing sophisticated SQL code...
_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
