Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

  • LANSA has implemented strong typing for all field types.
  • Alpha, String, and Char are all classed as String types and are valid for LANSA arguments of type 'A'.
  • Packed, Signed, Float, and Integer are classed as Numbers and are valid for LANSA arguments of type 'N'.
  • All other types like Date, DateTime, and BLOB are classed as their own type and are not valid for either a type 'A', or type 'N'.
  • Use of Hex 00 is not supported by LANSA in Alpha, String, Char, NVarChar, and NChar fields. The behavior will vary depending on what platform you are on and the database you write the data to. The use of hex 00 in Alpha working fields where overlays are used may have a valid purpose in RDML on IBM i, but it is up to you to ensure that the LANSA behavior meets the needs of the application on all platforms and databases where the application may run.
  • Field types have a default property, usually. Value, and additional properties as required.  For a Date field #MyDate, the following examples all have identical meaning:

...

  • Rather than the default property .Value, fields of type BLOB and CLOB have a default property called .FileName clearly indicates that changing the field's " value " is actually changing its default property, which is a file name property.
  • Fields that are SQL-nullable can be tested with *IS or *ISNOT *SQLNULL, and also have an intrinsic property called .IsSqlNull. This can be used to determine the current state of the field. For example:

...