Hello,
do you plan to implement SavePoint (as in TClientDataset) in your MemDataset (and in TUniTable, TUniQuery).
Thanks a lot
Zdenek
SavePoint in MemDataset
Hello,
my goal is to change TClientDataset-TProvider-TSQLQuery to TUniQuery in all our application (600k lines of code). Now we are using dbexpoda and dbexpress is not very efficient (by its architecture from Borland, not problem of dbexpoda).
But we need use the following features of dataset:
- AddIndex, DeleteIndex, IndexName (on client side, also unique index for duplicity tests, more indexes at time)
- SetRange, CancelRange
- CloneDataset (to save memory)
- SavePoint (discussed above)
Can we discuss the following features to be added to TMemDataset?
Thanks
Zdenek
my goal is to change TClientDataset-TProvider-TSQLQuery to TUniQuery in all our application (600k lines of code). Now we are using dbexpoda and dbexpress is not very efficient (by its architecture from Borland, not problem of dbexpoda).
But we need use the following features of dataset:
- AddIndex, DeleteIndex, IndexName (on client side, also unique index for duplicity tests, more indexes at time)
- SetRange, CancelRange
- CloneDataset (to save memory)
- SavePoint (discussed above)
Can we discuss the following features to be added to TMemDataset?
Thanks
Zdenek
We'll not add these features in the nearest future because currently we have some tasks with more priority.
You can use TUniQuery with TClientDataSet and TProvider components in cases when you need these features. Set the UniDirectional property of TUniQuery to True when it is used with TClientDataSet.
You can use TUniQuery with TClientDataSet and TProvider components in cases when you need these features. Set the UniDirectional property of TUniQuery to True when it is used with TClientDataSet.