There are products that act as middlemen between you and the Database. They
also offer database object abstraction (so you can have an object
representing table data. You define field -> property mappings, and the
product handles the transfer of data.)
These products usually have built-in caching.
Two products are
TopLink (expensive, but nice) http://www.objectpeople.com
VBSF (pretty inexpensive, and still nice) http://www.objectmatter.com
-----Original Message-----
From: Neal Kaiser [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 05, 2001 10:49 AM
To: Orion-Interest
Subject: ResultSet Caching
Does Orion have any built in caching functionality? Let's
say I have a
database query which returns 1,000 records and the user will
page thru 100
at a time. Instead of re-issuing the query each time (each
page), is there
some sort of cache object? How do you guys typically handle
this?
Thanks, Neal
