This is an issue that's been brought up before, but I think should have another look again.
If inconsistent fields are mapped together and data that cannot be stored in the target field goes into this field, the script will crash. This crash is necessary and can only be done at run time since the other option would have to be processing the entire source data set after each new method is applied.
My question is this: as I'm building the unit tests, should I assert the script crashes successfully with incompatible fields or is that not the desired behavior we want?
@pLeBlanc93 brought up the option of a "Validate" command which would run through the mapping and verify that the data will append correctly. This could
save users from the nasty python error they would get otherwise
save them from unexpected crashes. If a user is planning on appending huge data tables together overnight, they should have a way of making sure it wont crash 3 hours in.
This is an issue that's been brought up before, but I think should have another look again.
If inconsistent fields are mapped together and data that cannot be stored in the target field goes into this field, the script will crash. This crash is necessary and can only be done at run time since the other option would have to be processing the entire source data set after each new method is applied.
My question is this: as I'm building the unit tests, should I assert the script crashes successfully with incompatible fields or is that not the desired behavior we want?
@pLeBlanc93 brought up the option of a "Validate" command which would run through the mapping and verify that the data will append correctly. This could