I'm with you on that - use what one knows of mysql to get a bulk data block, then use chunk expressions to further parse.... I used to feel guilty that I didn't do it all in MYSQL, using views and other tricks, but these days I'm ok with it.
On Fri, Jan 2, 2009 at 6:31 PM, Sarah Reichelt <sarah.reich...@gmail.com>wrote: > I have done a similar thing in the past due to my lack of expertise > with SQL. I did an initial SQL query to get set of data that included > all that I needed but had more. That gave me a variable (I didn't use > files) which I processed further using Revolution. This was very fast > however an SQL expert might have been able to do the same thing in > pure SQL. I tend to think that the server connection is most likely > the slowest part of the operation, so any method that reduces the > amount of data to be transmitted is a good thing. But this has to be > balanced against processing times. > > Anyway my advice is to benchmark the different approaches and see what > works best in your particular circumstance. > > Cheers, > Sarah > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > -- Stephen Barncard ------------------------- San Francisco _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
