HP3000-L Archives

August 2003, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Alexander Zemerov <[log in to unmask]>
Reply To:
Alexander Zemerov <[log in to unmask]>
Date:
Wed, 6 Aug 2003 09:47:17 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
 Hi,

I use MB Foster UDALink v7.00.1 ( + Borland BDE ).
The only I need is to read data from huge table. But when I fetch
records, my application allocates more and more memory. This memory is
released only after dataset is closed. In case of small table it is
not problem, but when I load data from huge table appliccation
allocates up to several hundreds megabytes of memory.

It looks like MB Foster returns dataset in "select-for-update" or
"bi-direction" mode and caches ALL fetched data in the memory. I
really need "read-only" and "unidirect" mode, so I tried to manipulate
with dataset's "Request Live" and "Unidirectional" properties, but
always got the same behavior.
I don't think it is BDE problem, becouse it works fine with other ODBC
sources.

So question is - is there any possibility to force UDALink to not
cache all fetched records in the memory?

Sincerely,
Alexander Zemerov.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2