Xailer & OZ Software

I'm having problems with how to interface large MySQL datasets. Then I saw
how EMS Sql Manager (www.sqlmanager.net) is doing it, and I think that is
the way to go.
On the attached picture you see the heading of a browse in EMS. The browsed
table contains 800.000+ rows/records. The thing is that EMS automatically
limits the number of rows fetched by using the SELECT ..... LIMIT clause.
The default LIMIT is 1.000 rows/records, so at no point there will be no
more rows/records than the LIMIT in the dataset (the current LIMIT is seen
in the middle of the green SKIP-LIMIT buttons on the picture).
HERE IS THE MAIN POINT:
When setting filters and/or searching for something the WHOLE table is taken
into consideration, not only what is currently in the LIMITed dataset. So
my question is: How can we do that with TDataSet's in Xailer? (i.e. only
have a sub-dataset in the dataset, and do all filtering/searching on the
whole *table*)
I'm using MySQL (v5.0x).
(I've tried f.ex...
oTSQLQuery:Close()
oTSQLQuery:cSelect := "SELECT * FROM HugeTable LIMIT 0,<new limit>"
oTSQLQuery:Open()
....and it works, but the 'old' dataset is obviously not released as the app
in a while eats up all memory on the PC.)
Thanks a lot if anybody could point me in the right direction.
Paal


Attached files