I'm a huge fan of practical solutions, and this approach is definitely a good one if you are never going to be dealing with millions of records. Modern processing can do an awful lot without a "real" database muddying things up.

The only thing I would add is that if you ARE going to deal with really large data sets, the only real option is to re-factor your data with a database in mind. A well designed SQL database can definitely handle much larger sets of data much faster than Rev because it scales better for these tasks. That's not a knock on Rev it's simply what a database is designed to do. However, it make take an upfront investment is rethinking how you approach and structure your data.

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.

_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to