[
https://issues.jboss.org/browse/TEIID-3545?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3545:
---------------------------------------
Using the default keyword will require either significant parsing changes or a good bit of
validation to ensure the expression is not used in other contexts. Also adding support
for DEFAULT VALUES seems low priority as it would not be often used.
That leaves:
- allowing the default value to be a Teiid expression (this may require extension metadata
for backwards compatibility and some sources use special values)
- allowing the source query to use the source default, rather than using a default
specified in Teiid. This will also likely require extension metadata and/or an import
option to not set the default value.
Improvements in default handling
--------------------------------
Key: TEIID-3545
URL:
https://issues.jboss.org/browse/TEIID-3545
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12
The current default field is just a string value and captured as a string value at import
time - in general it should be allowed to be an expression. Also our insert syntax should
support the default/defaults keywords and be able to propagate that to the source, rather
than using the default on the model.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)