Form Caches: Difference between revisions
From IHRIS Wiki
No edit summary |
|||
Line 4: | Line 4: | ||
==Hippo Table Structure== | ==Hippo Table Structure== | ||
If a form XXXXX has a field YYYYY then the hippo_XXXXX table will have a column `XXXXX+YYYYY.` There is also a column `XXXXX+id` containing the id of the form and a column `XXXXX+parent` containing the parent form, if any. | If a form XXXXX has a field YYYYY then the hippo_XXXXX table will have a column `XXXXX+YYYYY.` There is also a column `XXXXX+id` containing the id of the form and a column `XXXXX+parent` containing the parent form, if any. | ||
==Cache Times== | ==Cache Times and Command Line== | ||
The background process | The hippo tables are generated by a background process once a form cache is consider stale. See the [[Configuring Form Cache Generation Timing]] document for information on timing for form caches and information on manually creating the form caches from the command line. | ||
[[Category: Technical Overview]] | [[Category: Technical Overview]] |
Revision as of 10:25, 3 March 2010
The data for a form XXXXX may be cached into a table hippo_XXXXX. This hippo table can be used for:
- To generate reports to Custom Reporting
- To export data for decentralized data management
Hippo Table Structure
If a form XXXXX has a field YYYYY then the hippo_XXXXX table will have a column `XXXXX+YYYYY.` There is also a column `XXXXX+id` containing the id of the form and a column `XXXXX+parent` containing the parent form, if any.
Cache Times and Command Line
The hippo tables are generated by a background process once a form cache is consider stale. See the Configuring Form Cache Generation Timing document for information on timing for form caches and information on manually creating the form caches from the command line.