----- Original Message -----
Sent: Wednesday, June 28, 2006 10:27
AM
Subject: [cfaussie] Re: QofQ
As someone who does not use QoQ that often, here are some other
ways you can do this:
- If you want to look up a certain value, create a referential
struct based on the column you wish to lookup, containing the vital
information
- If you want to create little queries, you could try query
functions (querynew, queryAddColumn etc)
- You could try converting the query into an array, CFC,
function or other structure that retrieves data in a
more relevant way
- Use query caching and the startrow / endrow features of
cfloop
- Do lots of little queries with the database instead of
continually messing around with one big query stored in
memory
CPU and memory are different things. Someone with a CS degree
should clear that up for you. Storing data in memory doesn't mean that you
avoid processing the data when you start using it in
QoQ.
I don't know why people use QoQ anyway. It seems limited compared
to other ways of processing data. That's just a personal opinion. I
know it's probably extremely useful in very specific
cases.
Joel
When running a page that uses excessive
QofQ from a single query the CPU goes bezerk. I was under the impression
that QofQ was simply accessing a recordset from memory. I have a
couple of questions if anyone has some ideas, workarounds for this.
Why does the cfstat utility record QofQ's as DB hits/sec? Also what
methods have ppl used to improve performance on pages that use a lot of
QofQ - where talking about 50 odd QofQ calls to a single
recordset.
TIA
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "cfaussie" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~----------~----~----~----~------~----~------~--~---