Currently (4.1) there seems to be a limitation that Order of columns in primary key constraint must match the order in which they're declared – any idea why and whether or not that are planes to

change this ?


we are using the bulk loader to load csv files and the columns order are in the order they appear in the file and not in the order of the key.


Alternatively, is would be nice to have the option to map the fields in the file to the columns so even if they are not in the order of the columns in the table we may still load the data to the right columns without the need to change the file




Information in this e-mail and its attachments is confidential and privileged under the TEOCO confidentiality terms that can be reviewed here.