avoid closing the dataset when losing connection to the data server
Posted: Sat 10 Mar 2018 23:43
doing some tests where:
1 - I define queries as cached update I linked a dbgrid to this query
2 - close the served firebird to simulate drop of connection
3 - when applying apply updates -> dbgrid closes because of the connection crash
5 - Then I put a DataSetProvider and a clientdataset in the form
6 - I connected the dataset provider to uniquery1
7- I connected the clientdataset to the datasetprovider
8- I changed the datasource of dbgrid to the clientdataset
9 - repeat steps 2 and 3 above.
dbgrid only closes if I move the complete data, but if I change a record in question and execute the applyupdates it does not close like using just uniquery with cached, why?
I know I can use disconnected mode, but I have tables with more than 50,000 records, and I noticed that it gets very slow to disturb.
can i use as i did with clientdataset?
Does anyone have a better tip to use with firebird?
fetchall is out of the question here.
disconected mode would be the solution if it were not so slow to open the tables, even with fetchrows set to few records.
how to use tdatasetfield with unidac and clientdataset without being slow to the point of application hang, because even configuring fetchrows and packed records, it takes so long to hang the application. I need a solution that is not using disconected mode because it also leaves the application slow.
1 - I define queries as cached update I linked a dbgrid to this query
2 - close the served firebird to simulate drop of connection
3 - when applying apply updates -> dbgrid closes because of the connection crash
5 - Then I put a DataSetProvider and a clientdataset in the form
6 - I connected the dataset provider to uniquery1
7- I connected the clientdataset to the datasetprovider
8- I changed the datasource of dbgrid to the clientdataset
9 - repeat steps 2 and 3 above.
dbgrid only closes if I move the complete data, but if I change a record in question and execute the applyupdates it does not close like using just uniquery with cached, why?
I know I can use disconnected mode, but I have tables with more than 50,000 records, and I noticed that it gets very slow to disturb.
can i use as i did with clientdataset?
Does anyone have a better tip to use with firebird?
fetchall is out of the question here.
disconected mode would be the solution if it were not so slow to open the tables, even with fetchrows set to few records.
how to use tdatasetfield with unidac and clientdataset without being slow to the point of application hang, because even configuring fetchrows and packed records, it takes so long to hang the application. I need a solution that is not using disconected mode because it also leaves the application slow.