Form Storage -- Magic Data: Difference between revisions

From IHRIS Wiki
Line 1: Line 1:
==Features==
==Features==
Storing form data in magic data is intended to be used in the following cases:
Storing form data in magic data is intended to be used in the following situtations:
*centrally maintained data that does not change frequently
*centrally maintained data that does not change frequently
*data that you want translations/localizations for
*data that you want translations/localizations for
*data that you do not care to track the history of changes
*data that you do not care to track the history of changes
*data that you want to load in easily for a module


==Storage==
==Storage==

Revision as of 09:28, 4 June 2009

Features

Storing form data in magic data is intended to be used in the following situtations:

  • centrally maintained data that does not change frequently
  • data that you want translations/localizations for
  • data that you do not care to track the history of changes
  • data that you want to load in easily for a module

Storage

All the data for form $form is stored in the magic data instance at the path

/I2CE/formsData/forms/$form

with each node underneath corresponding to an instance of the form. For example, under

/I2CE/formsData/forms/gender

we have

F  => Array [
   'last_modified' => '2009-04-27 1:23:45'
   'fields' => Array [
         'name' => 'Female' 
     ]
]
M => Array [
    'last_modified' => '2009-04-27 1:23:45'
    'fields' => Array [
         'name' => 'Male' 
      ]
 ]