TOraQuery, memory consumption
TOraQuery, memory consumption
I'm using ToraQuery (ODAC6.25; Delphi 7) to receive hundred thousands of records from a simple table with SDO_Geometry data (triangles).
The properties unidirectional and readonly are set to true.
A simple browsing through the result records (from the first to the last record) needs hundreds megabyte of memory.
I read about the the problem that the memory will not be freed after the query closes but how can I prevent the growing memory consumption?
Thank you in advance.
The properties unidirectional and readonly are set to true.
A simple browsing through the result records (from the first to the last record) needs hundreds megabyte of memory.
I read about the the problem that the memory will not be freed after the query closes but how can I prevent the growing memory consumption?
Thank you in advance.
Please see my answer at the following topic:
http://crlab.com/forums/viewtopic.php?p=32105#32105
http://crlab.com/forums/viewtopic.php?p=32105#32105
I've tried this already before I posted my problem here, but
this didn't solve my problem.
My problem is at first the dramatically growing of the memory consumption while browsing through the records . This process takes too much memory.
Is this problem solved too?
Any further hints?
Thank you in advance.
this didn't solve my problem.
My problem is at first the dramatically growing of the memory consumption while browsing through the records . This process takes too much memory.
Is this problem solved too?
Any further hints?
Thank you in advance.
-
Walter Weiss
- Posts: 7
- Joined: Tue 18 Dec 2007 13:39
TOraStoredProcedure
I've got the same Problem.
I'm using TOraStoredProcedure in Direct Mode with
ScrollableCursor := TRUE, ReadOnly := TRUE
when scrolling from first to last Position the Proceure crashes because of to less memory(2GigaByte).
Will the next Release fix this too?
I'm using TOraStoredProcedure in Direct Mode with
ScrollableCursor := TRUE, ReadOnly := TRUE
when scrolling from first to last Position the Proceure crashes because of to less memory(2GigaByte).
Will the next Release fix this too?