Join GitHub today
Torch schema exception on CustomTable Column definitions without a Set attribute #3838
There seems to be an issue in the released version of 3.6 where Torch throws an invalid schema exception for CustomTables which do not define the "Set" attribute on one or more Column definitions.
It seems to be an issue in how Light writes out unspecified Set attribute values to the .wixpdb file -- it writes an empty string instead of not specifying anything at all.
Passing the resulting .wixpdb into Torch results in the schema exception given above.
Here's an example... The names and descriptions are changed, but the table is as we've defined it.
I also noticed this same schema exception occurring in Light when consuming a .wixout file generated earlier by that same version of Light in order to generate the final .msi.
But, given it's likely an issue with how Light writes out such tables, it's not surprising the symptoms show up in more than one application.