Analytic supports the Number data type for representing various numeric values. The Number data type has three subtypes: Integer, Money, and Percent. The Number data type and all of its subtypes can be extended by using the addMethod and defmethod functions.
When to Use
The Number Native data type is a suitable container for numeric values. Several mathematical functions are provided by Analytic Information Server that perform several common computations.
The Integer Native Data Type are containers for whole numbers only. An Integer is a 32 bit integer value. The constant form for Integers are simple the number:
The Money Data Type are containers for monetary values. Money is an IEEE double precision real number representing U.S. currency values. Money constants can be written as signed whole numbers or signed fractions starting with the $ symbol. Normal arithmetic can be performed on the Money Data Type.
$-4.56 $1845 $345.89 $-192745
The Percent Data Type are containers for percentage values. Percent constants can be written as signed whole numbers or signed fractions ending with the % symbol.
2% -34% .02% 1.28%
Terminating a numeric constant with the percent operator has the effect of dividing the constant by 100.
The Number Data and all of its subtypes have constant forms. The Number Data type can be represented by scientific notation such as:
or as a real number:
or as a whole number:
Native Data Type
The Number Data Type is an example of an AIS Native Data Type.
Analytic Information Server stores all of its Native Data Types in Virtual Machine Containers. All containers are stored in memory. Containers provide the basic storage mechanism for modeling data of all types. Containers provide these fundamental characteristics:
Ability to hold any type of data (including code) at any time.
Ability to know what type of data is contained.
Ability to be stored, retrieved and evaluated by the system.
Ability to handle type conversion, and memory management automatically.
Containers come in two sizes, Large and Small. Small containers are six bytes in length, and large containers are ten bytes in length. Large containers can store larger amounts of data immediately and place less of a burden on the Heap manager. Small containers require less immediate space, but place more of a burden on the Heap manager.
Large containers can store the following data types immediately and does not require the services of the Heap manager:
Small containers can store the following data types immediately without placing additional burden on the Heap manager:
Analytic Information Server containers can be saved and loaded to and from persistent (database) storage at any time. Containers with immediate data are saved on disk in fixed length records equal to the size of the container. Containers with Heap object references are saved in fixed length records, which are automatically expanded to include the contents of the Heap object, and any objects referenced by the Heap object, etc. This feature is called Object Closure Management and is automatic with every Analytic Information Server container database save. Analytic Information Server containers may be loaded from any database repository record at any time. If the data in the record is immediate, the database load fills the container with the immediate data. If the data in the record is an object closure, the database load fills the container with a Heap object reference, and all of the objects in the record are loaded back into the Heap with the same referential relationships they had when they were saved.
The Number object can be demonstrated by the following functions.
The Number object can be demonstrated by the following examples.
|Example_Number_ isEven_001||Example_Number_ isExact_001||Example_Number_(sym)add_001||Example_Number_(sym)div_001|