We use UseUnicode=True and UnknownAsString=True, but the field is mapped as TStringField, it should be TWideStringField.
When set to True all character data is stored as WideStrings and TStringField is replaced with TWideStringFiled.
We are migrating the database fields from character(38) to native uuid fields and we expect the field mappings to be the same (or compatible).UnknownAsString (=True)
If True, fields of unknown data types are mapped to TStringField or TWideStringField depending on the value of the UseUnicode option.
I don't see any reason why the uuid fields would be mapped as TStringField on a Unicode database. It looks like a bug.
if anyone knows a way to workaround this, we'll apreciate it.
*A coworker already sent this problem to the support a week ago, but they don't answer.