dolt: Ambiguous error message when type checking fails makes it almost impossible to figure out why an import failed, especially when using triggers.

I ran into an issue attempting to load a csv file, which unusually hadn’t happened previously despite identical steps taken

After doing some investigation, it seems that new tables created with the below schema definition are not allowing me to import the attached csv. What is strange is that this previously worked fine, and I have located a particular branch on one of the test repos I had set up, where despite an identical schema the csv still imports.

Repo: geweldon/Source3 branch with error: main branch that still somehow works: history5

//Schema SBQQ__ProductOption__c @ working CREATE TABLE SBQQ__ProductOption__c ( Id varchar(18), OwnerId varchar(18), SBQQ__AppliedImmediatelyContext__c varchar(255), SBQQ__AppliedImmediately__c tinyint DEFAULT “0”, SBQQ__Bundled__c tinyint DEFAULT “0”, SBQQ__ComponentCodePosition__c decimal(6,0), SBQQ__ComponentCode__c varchar(60), SBQQ__ComponentDescriptionPosition__c decimal(6,0), SBQQ__ComponentDescription__c varchar(255), SBQQ__ConfiguredSKU__c varchar(18), SBQQ__DefaultPricingTable__c varchar(255), SBQQ__DiscountAmount__c decimal(14,2), SBQQ__DiscountSchedule__c varchar(18), SBQQ__Discount__c decimal(8,2), SBQQ__DiscountedByPackage__c tinyint DEFAULT “0”, SBQQ__ExistingQuantity__c decimal(12,2), SBQQ__Feature__c varchar(18), SBQQ__MaxQuantity__c decimal(12,2), SBQQ__MinQuantity__c decimal(12,2), SBQQ__Number__c decimal(5,0), SBQQ__OptionalSKU__c varchar(18), SBQQ__QuantityEditable__c tinyint DEFAULT “0”, SBQQ__Quantity__c decimal(12,2), SBQQ__QuoteLineVisibility__c varchar(255), SBQQ__RenewalProductOption__c varchar(18), SBQQ__Required__c tinyint DEFAULT “0”, SBQQ__Selected__c tinyint DEFAULT “0”, SBQQ__SubscriptionScope__c varchar(255), SBQQ__System__c tinyint DEFAULT “0”, SBQQ__Type__c varchar(255) DEFAULT “Component”, SBQQ__UnitPrice__c decimal(14,2), SBQQ__UpliftedByPackage__c tinyint DEFAULT “0”, CPQ_Custom_1__c tinyint DEFAULT “1”, CPQ_Custom_2__c tinyint DEFAULT “0”, Custom_Picklist__c varchar(255), Example_Record__c tinyint DEFAULT “0”, Pre_Existing__c tinyint DEFAULT “0”, ProdRecordSeedExtID__c varchar(255), ATGExtId__c varchar(255), ATGSourceId__c varchar(255) NOT NULL, PRIMARY KEY (ATGSourceId__c), KEY Id (Id), KEY OwnerId (OwnerId), KEY SBQQ__ConfiguredSKU__c (SBQQ__ConfiguredSKU__c), KEY SBQQ__DiscountSchedule__c (SBQQ__DiscountSchedule__c), KEY SBQQ__Feature__c (SBQQ__Feature__c), KEY SBQQ__OptionalSKU__c (SBQQ__OptionalSKU__c), KEY SBQQ__RenewalProductOption__c (SBQQ__RenewalProductOption__c) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

partner_org___dep_train_3-backup-sbqq__productoption__c-20220413205903.csv

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 36 (15 by maintainers)

Most upvoted comments

I have improved the error message you were getting to make future debugging easier. These changes have been merged to main, and will be usable next release (happening later today).

I made the same mistake, forgot that remote branches aren’t shown on clones by default.

We’ll get that error message fixed up in the next release, it should tell you the column and the value that failed. In the meantime we’ll figure out which value has the problem and let you know.