Home > Back-end >  TADOQuery how the query results are cached in the server, all don't get to the client
TADOQuery how the query results are cached in the server, all don't get to the client

Time:09-24

A 32-bit system, 4 gb of memory,
Use ADOquery lookup table data, there are an estimated 4 million, queries to the client after the memory, overflowing takes up about 2.5 G memory program was hanging off,
Due to business reasons, cannot do paging query,

Have similar caching mechanism, the data do not take to the client, cache server?

CodePudding user response:

Do you want to function is not paging?

CodePudding user response:

As if ADO does not support this, BDE support, and the result is parts are coming,
On the other, detected 4 million records will have what meaning?? Human can't all see,

CodePudding user response:

You still take the way of the paging to query,

CodePudding user response:

Still take pages or other forms to solve, after all, so many data can't be artificial view, but also conducive to check,

CodePudding user response:

Paging business reasons, can't do?

What exactly is the look of the business cannot be paged?
  • Related