Teiid DDL Parser Problems Found When Integrating With Teiid Designer

I provided the Teiid Designer team with locally built alpha 3.2 jars and am helping them integrate their DDL importer with the new Teiid DDL parser. These jars replaced old 2.x jars so there were other changes they needed to make.

Here are the problems found so far:

• the visibility of TeiidDdlLexicon constants need to be public since the Designer importer needs to know the Teiid node type and mixin names. These constants are currently scoped package private.

• the TeiidDdlLexicon constants with names containing "NODE_TYPE" should be renamed to not include "NODE_TYPE" in their name. Those constants at one time represented node type names but now are mixin names.

• the property "teiidddl:canBeNull" of the "teiidddl:resultColumn" mixin defined in the TeiidDdl.cnd can be deleted as it is not used. The "ddl:nullable" property is used instead.

• the Teiid DDL constraint type of "INDEX" can reference zero or more columns. The current TeiidDdl only considers the zero reference case where an expression is used. Both the CND and the parser need to be changed to fix this.