On Thu, 2 Aug 2001, Perrin Harkins wrote:
I've had great success with Select and cache only the row keys, fetch full
rows as needed. We were also caching the individual records (in
BerkeleyDB), so some pages never needed to hit Oracle at all after the
initial query. A good way to go, if
On Thu, Aug 02, 2001 at 07:10:49PM +0300, raptor wrote:
This may be of interest:
http://search.cpan.org/doc/TIMB/DBI_Talk5_2001/sld059.htm
]- Where is $h-{FetchHashKeyName}, I didn't found it even in the source
perl -m DBI my version is 1.18
Umm, let's see... that talk was given
On Thursday, August 2, 2001, at 04:07 AM, Joachim Zobel wrote:
One of the really nice features of MySQL (OK, its not a real RDBMS,
but who cares:) is LIMIT.
Using Oracle I have found it a real pain to display search results in
pages (of eg 20) while using connection pooling. The problem
This may be of interest:
http://search.cpan.org/doc/TIMB/DBI_Talk5_2001/sld059.htm
]- Where is $h-{FetchHashKeyName}, I didn't found it even in the source
perl -m DBI my version is 1.18
Tim.
At 13:42 02.08.01 -0400, you wrote:
At 1:07 PM +0200 8/2/01, Joachim Zobel wrote:
Hi.
One of the really nice features of MySQL (OK, its not a real RDBMS, but
who cares:) is LIMIT.
Using Oracle I have found it a real pain to display search results in
pages (of eg 20) while using connection
