Data Type Conversions

Following the introduction of data type inheritance, information stored as one data type can now be converted to another automatically within HASH for use in operations/calculations, or to normalize the appearance of data from across multiple entities stored divergently. To achieve this, a conversion "mapping" is stored from one data type to another "canonical" one within a group.

For example, children of the Length data type may include:

• →

  metric lengths stored as Centimeters (cm) or Milimeters (mm)

• →

  imperial lengths such as Feet (ft) and Inches (")

• →

  less common, specialist measures like Rack units (U) (commonly used in data centers) and Light-nanoseconds (the distance which a photon can travel in one billionth of a second).

Rather than require each data type to be mapped to each other data type, all conversions are routed via the "canonical" data type within Length.

In traditional datastores, when dealing with entities (rows) whos units of value are mixed, sorting a single column's values in ascending or descending order becomes a complicated multi-step job. In contrast, with convertible data types in HASH, the process requires no extra effort at all.

Convertible data types are also used by HASH's AI workers when conducting research and inferring data no your behalf. Their utilization vastly improves AI's ability to reason about inconsistently-formatted data, such as that found on the world wide web whose units of value and presentation differs across websites and even pages on single sites.

Other misc improvements

• →

  Inline errors: Validation errors are now shown when updating entities where required properties are missing, and when the minimum or maximuim number of items allowed in an array fails to match the number that are present.

• →

  Multi-file upload: Where multiple files are accepted for upload, these can now be selected and uploaded all at once, rather than individually.