#3 DDL Generation Error for Large Length data type

[John Miller]

When generating DDL for a large length data type the
code for SQL Server is:

FieldName NATIONAL CHARACTER VARYING() NOT NULL,

It should be:

FieldName NATIONAL TEXT NOT NULL,

This applies to SQL Server, Oracle, PostGre, DB2 &
Standard SQL

jMM

[Kevin M. Owen]

Logged In: YES
user_id=1014759

This is one of several known issues with the current data
type mapping in the tool.
Data types are being completely revamped for ORM2, and the
new data types are already being used by the various
generation components. However, the tool itself is still
using the old Visio-style data types, and the generation
components perform only very basic mappings from the old
data types to the new data types.
In our next release, the tool will likely be using the new
data types directly, and far more robust mappings will be
performed when importing old Visio models.

[Brian Nalewajek]

Logged In: YES
user_id=1501525

Hi,
I also noticed that the .sql file generated by
ORMCustomTool, didn't catch that a length field entry was
required for National Character Varying type. Once I
figured that out, the 'create schema' for a test ORM model
I made executed properly. BRN..