[ https://jira.jboss.org/browse/TEIID-1106?page=com.atlassian.jira.plugin.s... ] Work on TEIID-1106 started by Van Halbert. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIID-1106?page=com.atlassian.jira.plugin.s... ] Steve Hawkins updated TEIID-1106: --------------------------------- Fix Version/s: 7.2 (was: 7.1) Pushing to 7.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIID-1106?page=com.atlassian.jira.plugin.s... ] Van Halbert commented on TEIID-1106: ------------------------------------ When importing via the Designer, the name-in-source is surrounded in tic marks because the name contains a special character (i.e., nt:base becomes 'nt:base'). Changes had to be made to strip the tic marks prior to pushing the sql to ModeShape -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIID-1106?page=com.atlassian.jira.plugin.s... ] Steven Hawkins commented on TEIID-1106: --------------------------------------- PATH, NAME, LOCALNODENAME, DEPTH, and SCORE will be available as pseudo-columns (e.g. "nt:base"."jcr:path"). An additional pseudo-column "jcr:properties" will be available for use by in functions that expect a table reference. ModeShape will expand it's JCR2 implementation to handle these columns. The ModeShape JDBC driver will need an option to expose the pseudo-columns through the JDBC metadata, otherwise the Designer or the translator would need to add them (in the latter case, a Modeler import would use a dynamic VDB connecting to ModeShape, which is less than ideal). Teiid UFDs will be created for CONTIANS, ISCHILDNODE, ISDESCENDENT, ISSAMENODE, REFERENCE. Each will be prefixed with JCR_. The JCRFunctions.xmi file will be put along side the OracleSpatialFunctions.xmi. We may want to kit these into a higher level location for convenience. The translator will expect specific pseudo-columns, such as JCR_REFERENCE(nt_base.jcr_properties) would become REFERENCE("nt:base".*) ModeShape will also support columns with a native type of REFERENCE or WEAKREFERENCE as automatically wrapped in a REFERENCE function. Other function support: LENGTH for strings only. UpperCase/LowerCase as UCASE/LCASE and the arithmetic functions. Literals: time/date/timestamp as a literal will be: CAST('literal' AS DATE) boolean as a literal will be: CAST('literal' AS BOOLEAN) The translator will also expect the driver to appropriately escape identifiers with double quotes on import. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1106?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1106. --------------------------------- -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira