[ https://issues.jboss.org/browse/TEIID-2012?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2012: ------------------------------------- "value" is reserved word. For all the reserved words see [http://anonsvn.jboss.org/repos/teiid/trunk/api/src/main/java/org/teiid/la...] For table names and column names only restriction is it can not contain period (.) in them. If the table/column name contains any reserved words or special characters then it MUST be enclosed in the quotes ("), then it will be allowed in the parser. Teiid will not add these quotes, as it will not know which is reserved word vs name, the client needs to add them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2012?page=com.atlassian.jira.plugin... ] Ted Jones commented on TEIID-2012: ---------------------------------- Ok cool... based on Steve's comments in TEIIDDES-1300 ("Also I'm not sure that you want to put quotes around the metadata names of columns that match keywords. As long as you construct sql strings with command language objects, we'll add the appropriate quotes for you.") I thought Teiid would add the quotes for the reserved words (at a minimum). Perhaps the SQL we are generating does not fall under the constructs Steve refers too. It's not an issue for us to do it when we generate the transformation. I'll close this Jira. Thanks Ramesh. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2012?page=com.atlassian.jira.plugin... ] Ted Jones commented on TEIID-2012: ---------------------------------- Steve, the observed errors are as I described above. We are setting the string value of the transformation in the editor, so we are not programmatically using language objects to generate the transformation. Perhaps that is where the process falls down? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2012?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-2012: ------------------------------------- +1 for handling in on the visitor side. Designer has been approaching these generated SQL templates as if the SQL was typed/pasted into our T-Editor by a user. Don't think we should start to programatically create Lang. Objs. now, else we'd regress in our quest to use Teiid SQL processing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2012?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2012. --------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira