Delphi: using TClient. Dataset as an in- memory dataset. TClientDataSet: How to keep local data save and available when a database structure has been changed.Graveyard stones below for some libre components. In times of Delphi 5/ Delphi 7 there were initiatives to make any object with published properties (more accurately - array or some collection of those) into a database. Though it leaves too much IMHO on developers shoulders. Client Dataset Indexes. When you load a client database from a file or a stream. Delphi provides a couple of different methods for retrieving index. TDBF. sf. net table had in- memory mode, but was early removed. TDBF is dead also. Lib/Jedi. VCL has Memory. Dataset. Though rx. Lib target was source- level compatibility since 1. Delphi 1 up to Delphi 5. That crippled the code much. In JVCL it had some attention and removing of aging code, but still is half- baked when needed some deeper than trivial usage. There are also free- for- personal DCU components like SQLMemory. Table, not for recent releases though. I wonder if Firebird Embedded / SQLite could be used to create in- memory table without using system- wide hacks like RAMdrive : -). Client. Dataset Load. From. File - delphi. Right here's an interesting one. I have a clientdataset that at some point through the program switches Log. Changes off. Then on close will save to a file (this saves everything in the dataset, original data and changes). Now at another point during the program I want to load that file back into the dataset and apply the changes. Unfortunately when you load the file back in, the clientdataset has no knowledge of the delta. So although the data contains changes it doesn't know it, therefore when an Apply. Updates is called no data is sent. It would be completely mad to send all the data, so does anyone have any suggestions on getting round this problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |