Changes

Jump to: navigation, search

IMSMA Staging Area

389 bytes added, 12:58, 19 June 2014
no edit summary
| align="left" | The Land object has a multi-select attribute called ''Marking'' (Marking Method). In the staging area, the HAZARD table has an attribute marking_method with a comma-separated list of values, for example 'Official Signs, Local Signs'. Additionally, the table HAZARD_STD_MULTISELECT can be joined with the HAZARD table in order to get to the same values as rows. Reusing the above example, there will be two rows, one with 'Official Signs' and one with 'Local Signs' as values (or the translated values if any translations are available).
|-
| align="left" | '''Standard text, numeric, date and time attributes''' | align="left" | Stored directly in the main object table (as opposed to {{IMSMANG}} where a lookup has to be made through the <OBJECT>_HAS_CDFVALUE, CDFVALUE and CUSTOMDEFINEDFIELD tables)| align="left" | Each CDF will be turned into a column in the staging area. For example, a CDF called ''My Hazard CDF'' defined on Land will result in a column named my_hazard_cdf in the HAZARD table of the staging area. {{Note | Note that non-standard characters in CDF names, such as blanks, are replaced by underscores in the column names}}|-
* CDF text, numeric, and any single-select attribute values are stored directly in the main table.
** Example:
* Standard multi-select attribute values are directly stored in the main table as a comma-separated list '''and''' in a normalised way in the standard multi-select table associated to the object.
** Example:
* CDF multi-select attribute values are directly stored in the main table as a comma-separated list '''and''' in a normalised way in the CDF multi-select table associated to the object.
** Example:
1,068
edits

Navigation menu