Sorry for the delay, We have a small driveway and neighbors (providence RI) with Prius's and Jetta's that cannot move, Me, I have a 4x4 dakota and have to pull everyone to safety :)
I was raised in Wyoming so I am used to the snow, but everyone around me would be found in the spring thaw if they did not have plows and a Starbucks down the street. :) The loop sounds like a better idea to me personally. If the initial query already has the data, then just loop over it, even if there are hundreds of records it will be trivial, especially if you create functions or services to handle the work for the timestamps comparisons. You would be better off just looping through the raw query initially, then use a custom method to loop from 1-60 (if thats what you need) instead of looping over the nested query loop 60 times. But again, you should be concentrating on getting it to work first, then worry about the performance when it is an issue. There are many ways to cache the results if needed, and you can optimize it when and if you need to. -- /Kevin Pepperman -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
