ENABLE INTEGERS - Oracle Integers when exporting to Aurelius Classes

BIZ TMS Data Modeler
1

Aurelius and Data Modeler are beautiful things.

For backward compatibility and future INTEGER types, can ENABLE INTEGERS be available in general Settings when exporting to Aurelius Classes.

Oracle has integers types. Currently for Aurelius it always maps to Double. :(
Oracle column type for Aurelius Integer will be: NUMBER (x,0) or NUMBER (x) Where x <= 18.
Oracle column type for Aurelius Int64 will be: NUMBER (19,0) or NUMBER (19).
Oracle column type for Aurelius Double will be: any other NUMBER column type.

For reference: BDE would handle Integers from Oracle perfectly if ENABLE INTEGERS = True for the Native Oracle driver property. Set in BDE config.

Full list of Oracle Integer types for knowledge: Example NUMBER(3) and Number(3,0) are the same..

MSSQL / ORACLE / DELPHI / Aurelius Field Property Type
TINYINT/ NUMBER(3) / Int8 / INTEGER
SMALLINT /NUMBER(5) / Int16 / INTEGER
INTEGER/NUMBER(10) / Int32 / INTEGER
BIGINT/NUMBER(19) / Int64 / INT64
Any other oracle NUMBER type is Double

2

You can manage this using customization scripts in TMS Data Modeler.

Here is an example:

procedure OnColumnGenerated(Args: TColumnGeneratedArgs);
var
  NewType: string;
begin                
  if (Args.DBField.DataTypeName = 'Number') and (Args.DBField.Size2 = 0) then
  begin
    if Args.DBField.Size <= 10 then
      NewType := 'Integer'                          
    else        
      NewType := 'Int64';
    if not Args.DBField.Required then
      NewType := 'Nullable<' + NewType + '>';
    Args.Field.FieldType.BaseType := NewType;
    Args.Prop.PropertyType.BaseType := NewType;
  end;                  
end;
3

This works for me. But it doesn't respect the Export forms checkbox for:
Don't use Nullable

4

You can then simply remove that part from the script.