[teiid-issues] [JBoss JIRA] (TEIID-1834) Add support for a comparable binary type

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-1834:
----------------------------------

    Attachment: varbinary.patch


Here's the initial implementation.  Still waiting on designer team for an impact assessment and also need to update the system vdb datatypes index - but that seems like I'll need to use an older designer and modify the built-in types xsd.

This batch also makes another attempt at consolidating type code.  However we still have things spread out over:

TypeFacility
BatchSerializer
SizeUtility
DatatypeManager
JDBCSQLTypeInfo

any necessary transforms
the type class
system vdb datatypes

plus any misc handling in string handling, translators, and the driver.
                
> Add support for a comparable binary type
> ----------------------------------------
>
>                 Key: TEIID-1834
>                 URL: https://issues.jboss.org/browse/TEIID-1834
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.0
>
>         Attachments: varbinary.patch
>
>
> Teiid currently lacks a binary/varbinary type.  Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string.  It would be a comparable type and need an escape syntax for entering literals.  Translators would need to be modified to account for binary literals.
> See the forum post for current workarounds.  We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248.  Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata.  We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format.  The advantage of this latter approach is that there is nothing more that designer must do to support this case.  The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering.

--
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