>than
>doing so for an array, especially when you take the listtoarray()
>conversion
>time into account. Also, why not create a virtual query and do a QofQ
>rather
>than using a real table and a bulk upload?
It's quite possible you're right that sequential access using a list is
faster than using an array. As I said, I didn't actually implement this. My
own experience is that using Listfind() for even a small list is really
really slow, but of course, that is not sequential access.
The advantage of a SQL based approach as versus a looping approach is that
if any more requests are made, it's a lot easier for me to write a line of
SQL as opposed to 20 lines of cf loops. While both a db and QofQ are
SQL-based, QofQ has both performance problems and sql functionality
problems. If the query gets complicated, QofQ might not accept it. I'd
rather not explore the limits of QofQ for anything other than a small query.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
