Problems with fetchAll=false
Posted: Wed 21 Sep 2011 13:43
Because of the bigger flexibility we decide to change from DBISAM to UniDAC. In our first tests we made some first experiances by simple opening tables.
Basis
We took a dbgrid, datasource and Unitable
We choose a datatable with about 150000 rec
DBMS: MySQL 5.5.13
1. Fetchall = true
We choose fetchall=true to see all the data
We wait about 30 sec
This is what we normaly want but it tooks to much time. With DBISAM this tooks about 1sec.
2. Fetchall = false
same components
We choose fetchall=false to see only 25 Records
We wait less then 1 sec
This would be ok too, but when we now want to edit,delete or post there comes an error that fetchall doesn't work with lockmode pessimistic.
When I change the lockmode to lmNone or lmOptimistic we can edit, delete or post but then there is no more lock on the record and inconsistent data might be created.
Our question: Is there a way to increase the speed of opening tables larger than 100000 record fetchall=true? Or is there a way to use fetchall=false by keeping the lockmode pessimistic?
Basis
We took a dbgrid, datasource and Unitable
We choose a datatable with about 150000 rec
DBMS: MySQL 5.5.13
1. Fetchall = true
We choose fetchall=true to see all the data
We wait about 30 sec
This is what we normaly want but it tooks to much time. With DBISAM this tooks about 1sec.
2. Fetchall = false
same components
We choose fetchall=false to see only 25 Records
We wait less then 1 sec
This would be ok too, but when we now want to edit,delete or post there comes an error that fetchall doesn't work with lockmode pessimistic.
When I change the lockmode to lmNone or lmOptimistic we can edit, delete or post but then there is no more lock on the record and inconsistent data might be created.
Our question: Is there a way to increase the speed of opening tables larger than 100000 record fetchall=true? Or is there a way to use fetchall=false by keeping the lockmode pessimistic?