[
https://issues.jboss.org/browse/TEIID-3110?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3110:
---------------------------------------
Alternatively we can look at keeping the current ddl behavior and have the name in source
default to the name. With the exception of ldap, the other translators like
saleforce/odata simply require the name in source to be populated. However the ldap logic
looks like it needs to differentiate between the null and the same name case, so it seems
like the better path is just not omitting the name in source from the ddl.
name in source should not be omitted in ddl
-------------------------------------------
Key: TEIID-3110
URL:
https://issues.jboss.org/browse/TEIID-3110
Project: Teiid
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Query Engine
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.9
When creating the ddl string we'll omit the name in source if it matches the table
name. While this is valid for several translators (jdbc, object, mongodb, and others), it
is not valid for all - salesforce, ldap, odata, and others.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)