DDL Parser Should Use JCR Substitution Characters When Creating A Node With A Name Containing Illegal JCR Characters

Using a Teiid Designer test database I ran into a table called "Product.product:info." That table had columns with names containing the ':' character also. The DDL parser framework does not handle names with illegal characters.

The DDL parser framework should be changed to use the JCR substitution characters when creating a node if the name contains illegal characters. The framework should also provide a way to obtain the original name.