> They are cached by name, search parameters, and also by the query
> structure itself.
>
> So
>
> SELECT product_name
> FROM products
>
> and
>
> SELECT product_name FROM products
>
> would be read as 2 separate queries because the structure is
> different, even if they are named the same.
Oh I see - didn't realise that.
>
> Where it will also help, in addition to static queries, is if you
> have a query that returns many items and you are doing next'n
> records. Every time the user clicks to show the next
> startrow/maxrows, the database will not be hit again and it will
> speed things up considerably.
Excellent. I basically have 2 queries that both return large amounts of
records - the first being as you describe above - however the second is an
interesting dilema. I have a table called Locations, with "County" and
"Town." Using the cool TwoSelectsRelated tag, I'm populating both boxes
(users choose a county - and then a town). However with a current town list
of over 1600, and due to the fact that TwoSelectsRelated loads both columns
of the table in their entirity, this takes *ages* to download. Using
TwoSelectsRelated is by far the nicest option available - but unfortunately
I might have to change.
Hopefully caching the query will speed things up a little anyhow..
Cheers,
Will
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
