Does anyone know what the implications of using ClientDataSets now that Embarcadero is looking to replace dbExpress with the AnyDAC components? I've never used AnyDAC so I don't know if AnyDAC uses its own in-memory table component or whether it integrates with the CDS.
You can use a TClientDataset with any TDataset descendent so it should be business as usual.
ReplyDeleteSo it's AnyDAC TDataset component --> TDatasetProvider --> TClientDataset. Is that right?
ReplyDeleteAlso I'm assuming that ApplyUpdates, etc will still work as well.
i think it will work like that, because TClientDataSet connect to TDataSetProvider and TDatasetProvider connect any TDataset descendent, so i think we can still use TClientDataSet, but i read that AnyDAC can also connect to Datasnap, that one i still don't understand
ReplyDeleteI can only comment on our usage, which was as a BDE replacement, but the AnyDAC query component essentially wraps the dataset/provider/memtable into a single component, which as DA-SOFT would say, this it the normal, everyday component you would use for most tasks. It is possible to handle all of the individual pieces yourself to do much more complicated tasks, but I have to think this is rarely done because the query component is so powerful already. BTW, DA-SOFT is deservedly proud of their memtable implementation, which is also a stock component in their tool chest. I found this old post with a 5 second search, there are probably fresher benchmark numbers and info, though this page also gives a glimpse into the architecture of the product. http://www.da-soft.com/blogs/anydac-vs-kbmmemtable-memtableeh-dxmemdata-clientdataset.html
ReplyDeleteDan Hacker Thanks for the link! It looks like the AnyDAC components have got it all covered.
ReplyDelete