> Caching a query and using the blockfactor to employ a "Get
> next n records" is a really easy thing to implement. Its easy
> to code, easy to use, easy to maintain, easy to
> understand....i guess i dont see where the complexity comes in?

It's worth pointing out that the BLOCKFACTOR attribute doesn't have anything
to do with caching recordsets - it simply specifies the size of the buffer
used to transfer records from the database to CF.

But in general, you're right, there isn't a whole lot of complexity to using
CACHEDWITHIN/CACHEDAFTER.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to