Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Torch schema exception on CustomTable Column definitions without a Set attribute #3838

Closed
wixbot opened this Issue Nov 17, 2012 · 13 comments

Comments

Projects
None yet
2 participants
Collaborator

wixbot commented Nov 17, 2012

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.

example:
error TRCH0107 : Schema validation failed with the following error at line 1, column 18611: The 'set' attribute has an invalid value according to its data type.

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.

That is:

  

Passing the resulting .wixpdb into Torch results in the schema exception given above.

Originally opened by rvdwagner from http://sourceforge.net/p/wix/bugs/3142/

Collaborator

wixbot commented Nov 22, 2012

Here's an example... The names and descriptions are changed, but the table is as we've defined it.

      <CustomTable Id='CustomTable'>
          <Column Id='Column1' Category='Identifier' Type='string' Width='72'
                        Description='The identifier for the row'
                        Localizable='no' Nullable='no' PrimaryKey='yes' />
          <Column Id='Column2' Category='Condition' Type='string' Width='255'
                        Description='A random condition'
                        Localizable='no' Nullable='yes' PrimaryKey='no'
                        Modularize='Condition' />
          <Column Id='Column3' Category='Integer' Type='int' Width='2'
                        Nullable='no' MinValue='1' MaxValue='9999' 
                        Description='A random value'
                        PrimaryKey='no' />
      </CustomTable>
Collaborator

wixbot commented Nov 22, 2012

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.

Collaborator

wixbot commented Nov 22, 2012

Please post your definition.

Collaborator

wixbot commented Nov 22, 2012

That was supposed to be: Please post your CustomTable definition.

Collaborator

wixbot commented Oct 17, 2013

Originally changed by barnson
Area set to linker
Release changed from v3.8 to v3.x

Collaborator

wixbot commented Dec 19, 2013

Originally changed by bmurri
AssignedTo set to wixsupport

Collaborator

wixbot commented Jun 12, 2014

This is still happening for 3.8. We're also not able to read the wixpdb file to try and work around it since it's in cab format.

Originally posted by djryan
Status changed from Open to Untriaged

Collaborator

wixbot commented Jun 12, 2014

Known issue, open to fixed in v3.x.

Collaborator

wixbot commented Jun 12, 2014

Originally changed by barnson
AssignedTo changed from wixsupport to bobarnson
Release changed from v3.x to v3.9

Collaborator

wixbot commented Jun 12, 2014

wixtoolset/wix3#64

Originally posted by barnson

Collaborator

wixbot commented Jun 12, 2014

Originally changed by barnson
Resolution set to fixed
Status changed from Open to Resolved

Collaborator

wixbot commented Oct 4, 2014

I downloaded 3.9 RC3 but am still getting this error. Has this not been fixed?

Originally posted by pezmannen

Collaborator

wixbot commented Oct 4, 2014

@pezmannen, it was fixed. Please provide a sample project that demonstrates the problem.

Originally posted by barnson

@wixbot wixbot added bug linker labels Dec 20, 2015

@wixbot wixbot added this to the v3.9 milestone Dec 20, 2015

@wixbot wixbot closed this Dec 20, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment