Clarion Community Help

Here are just some possible tasks for the In-memory driver.

·Use it instead of a global queue. You access it using standard Clarion File commands, and it is a thread-safe structure requiring no synchronization.

·Use it for the most intensely used areas of your application, where your users spend most of their time.

·Use it as a temporary table for Parent-Child relations, where the end user makes all changes to the child records in the In-Memory table. For example, new order items can be added and updated, and only when the invoice is actually saved, all of the child records can be written to the physical file in a single transaction along with the order record.

·Use it as a buffer for receiving SQL query results. After you have received the result set into the In-Memory table you can do sorting, filtering, perform QBE/QBF requests using standard browse box tools, without any additional access to the SQL server. This approach can dramatically reduce network traffic, and frees server resources as fast as possible.

·Using the In-Memory driver allows you to minimize the number of KEY and INDEX files in your physical tables. For example, if you have a rarely requested report that requires a special index, you can declare this index in the In-Memory table but not in the physical table. This way you can reduce required database resources and speed up data I/O operations.

·Eliminate file conversions of the physical table when you need to add a new key or index for a Report or Browse. Just add the new INDEX to the In-Memory table.

·You can construct your In-Memory table using several data sources, and the sources can combine data tables of various formats. For example, you can load configuration data from a mainframe file and combine it with additional items from a local file.