Data Modeler and Aurelius compatibility

[wlandgraf (Wagner Landgraf)]

Hello,

Foreign key names: You can tell Data Modeler to use the specified foreign key name in Aurelius by adding a customization script like this: Adding ForeignKey Attribute to Associations

Unique constraint names: For now, you can't provide Aurelius with the unique key name, indeed. Aurelius will create it using its own autogenerated name. This is a feature in our backlog to be implemented in feature.

Ansi/Wide strings: Aurelius consider all mapped string fields/properties as "ANSI" strings (Varchar). To tell Aurelius you want them to be considered "Unicode" (NVarchar), you can define the type of the field/property as Widestring, or you can enable a global config property MapStringToNationalChar thats tell Aurelius to treat all strings as NVarchar. Some references:

UTF8 Charset

That's by default. Any string property is mapped to "Ansi" (varchar) in database. I believe your database was not created by Aurelius, but instead was already created with types "NVarchar" instead of "Varchar"? IF that's the case, all you have to do is change a global configuration: uses Aurelius.Global.Config; TGlobalConfigs.GetInstance.MapStringToNationalChar := true;

Nationality characters encoding problem

How is your entity class declared? Try setting Name property to WideString type, or use uses Aurelius.Global.Config; TGlobalConfigs.GetInstance.MapStringToNationalChar := true;

Finally, Data Modeler provides the customization script feature which gives you full flexibility to fine tune your Aurelius output and have it automated at the same time so in every new generation your customizations will be applied through the script.