Correctly handle union types

OpenAPI spec allows union types, that is, a single field using different data types. To handle this, such fields should be represented as separate columns for each data type, with some automatically generated suffixes (numbers?), in a predetermined order (sorted by data type?).

Currently, only the first data type from a union is used, which is obviously wrong.