Top Section Deleted
Course VIII — Programming with the In-Memory Driver
Its primary function is to create and build a memory table without the need for any hand code to load and use the In-Memory table. You can optionally save the contents of the cached memory table to the original data source.
By definition, a generated IMDD table is one that is generated automatically by the IMDD template and the underlying FileSynchronization class library. Also by default, the generated table is filled (or loaded) at program start up. Typically you will be using In-Memory tables to cache data for fast lookups, and to improve performance on complex reports, but if you do allow updates to your IMDD tables learn how the Template also provides the option to write data from the Memory table back to the original physical file.
Dictionary Tables in the In-Memory Caching Support extension allow you to match a target data source (like a TopSpeed, Btrieve, or MS-SQL table) with an IMDD table defined in your data dictionary.
The InMemoryCachedtableLoad and InMemoryCachedtableSave code templates are used with any Dictionary cached table.
The interface is very simple, but the power behind them is not. You'll learn how to get the most out of these templates.
Practical examples using the IMDD around custom source code.
Using Triggers with the IMDD
Using the IMDD to "denormalize" tables
Storing IMDD record snapshots into a BLOB
Using the IMDD to process an SQL result set
Maintaining multiple tables with a Single IMDD table
A look at using BLOBs to snaphot and restore In-Memory tables.
If you are now using Clarion 6.2 with the IMDD Version 2.0, you now have a more powerful tool for processing any type of SQL queries into a result set that can easily be processed by the In-Memory Database Driver.
Copyright © 2011 Data Down Under
Designed by 1st Logo Design