[JBoss JIRA] (TEIIDDES-2660) Add support in Designer for foreign keys cross models
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2660?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2660.
----------------------------------
> Add support in Designer for foreign keys cross models
> -----------------------------------------------------
>
> Key: TEIIDDES-2660
> URL: https://issues.jboss.org/browse/TEIIDDES-2660
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 11.1
>
> Attachments: foreignKey.zip
>
>
> Add support in Designer for foreign keys cross models.
> In Designer you cannot have a FK cross models. That is not a limitation with DDL metadata in Teiid. It's a misstatement to relate that to optimization. If the PK/FK is present we'll use that information just as we would in a single source - we do not however enforce the FK. That can be done through the use of an update procedure though.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIIDDES-3071) SQL transformation editor rewrites TRIM() function incorrectly most of the time
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3071?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-3071.
----------------------------------
> SQL transformation editor rewrites TRIM() function incorrectly most of the time
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-3071
> URL: https://issues.jboss.org/browse/TEIIDDES-3071
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 11.0.1
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 11.1
>
>
> Paste the below SQL in the transformation editor to create a view table:
> SELECT
> trim(INTKEY),trim(STRINGKEY),trim(INTNUM),trim(STRINGNUM),trim(FLOATNUM),trim(LONGNUM),trim(DOUBLENUM),trim(BYTENUM),trim(DATEVALUE),trim(TIMESTAMPVALUE), trim(BOOLEANVALUE),trim(CHARVALUE),trim(SHORTVALUE),trim(BIGINTEGERVALUE),trim(BIGDECIMALVALUE),trim(OBJECTVALUE)
> FROM
> bqtora.LARGEB
> Once you save it, it gets rewritten with the defaults, but it leaves the column name out most of the time:
> SELECT
> trim(' ' FROM ), trim(' ' FROM bqtora.LARGEB.STRINGKEY), trim(' ' FROM ), trim(' ' FROM bqtora.LARGEB.STRINGNUM), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM ), trim(' ' FROM bqtora.LARGEB.OBJECTVALUE)
> FROM
> bqtora.LARGEB
> So obviously you receive a validation parsing error:
> ERROR: Error in parsing of sql - Encountered " ")" ") "" at line 2, column 31.
> Was expecting one of:
> "char" ...
> "date" ...
> "time" ...
> "timestamp" ...
> "cast" ...
> "convert" ...
> "any" ...
> "array_agg" ...
> "case" ...
> "exists" ...
> "false" ...
> "hour" ...
> "insert" ...
> "left" ...
> "minute" ...
> "month" ...
> "not" ...
> "null" ...
> "right" ...
> "second" ...
> "some" ...
> "translate" ...
> "true" ...
> "unknown" ...
> "user" ...
> "year" ...
> "xmlagg" ...
> "xmlcast" ...
> "xmlconcat" ...
> "xmlcomment" ...
> "xmlelement" ...
> "xmlexists" ...
> "xmlforest" ...
> "xmlparse" ...
> "xmlpi" ...
> "xmlquery" ...
> "xmlserialize" ...
> "xmltext" ...
> "instead" ...
> "enabled" ...
> "disabled" ...
> "view" ...
> "key" ...
> "serial" ...
> "textagg" ...
> "count" ...
> "row_number" ...
> "rank" ...
> "dense_rank" ...
> "sum" ...
> "avg" ...
> "min" ...
> "max" ...
> "every" ...
> "stddev_pop" ...
> "stddev_samp" ...
> "var_samp" ...
> "var_pop" ...
> "document" ...
> "content" ...
> "trim" ...
> "empty" ...
> "ordinality" ...
> "path" ...
> "first" ...
> "last" ...
> "next" ...
> "substring" ...
> "extract" ...
> "to_chars" ...
> "to_bytes" ...
> "timestampadd" ...
> "timestampdiff" ...
> "querystring" ...
> "namespace" ...
> "result" ...
> "index" ...
> "accesspattern" ...
> "auto_increment" ...
> "wellformed" ...
> "sql_tsi_frac_second" ...
> "sql_tsi_second" ...
> "sql_tsi_minute" ...
> "sql_tsi_hour" ...
> "sql_tsi_day" ...
> "sql_tsi_week" ...
> "sql_tsi_month" ...
> "sql_tsi_quarter" ...
> "sql_tsi_year" ...
> "texttable" ...
> "arraytable" ...
> "selector" ...
> "skip" ...
> "width" ...
> "passing" ...
> "name" ...
> "encoding" ...
> "columns" ...
> "delimiter" ...
> "quote" ...
> "header" ...
> "nulls" ...
> "objecttable" ...
> "version" ...
> "including" ...
> "excluding" ...
> "xmldeclaration" ...
> "variadic" ...
> "exception" ...
> "raise" ...
> "chain" ...
> "jsonarray_agg" ...
> "jsonobject" ...
> "preserve" ...
> <ID> ...
> <ESCAPEDFUNCTION> ...
> <ESCAPEDTYPE> ...
> <DECIMALVAL> ...
> <FLOATVAL> ...
> <STRINGVAL> ...
> <UNSIGNEDINTEGER> ...
> <BINARYSTRINGVAL> ...
> "(" ...
> "+" ...
> "-" ...
> "?" ...
> "$" ...
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIIDDES-3087) There isn't a way to set the Connection type on a VDB in the Designer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3087?page=com.atlassian.jira.plu... ]
Matej Kralik reopened TEIIDDES-3087:
------------------------------------
When I generate .vdb, vdb.xml in the META-INF doesn't contain any connection-type element. I must change connection-type in vdbEditor (vdbEditor.png) and after that, the vdb.xml in the .vdb contains this element. So if I wont to set NONE which is predefined, I must change the connection type to something else and back to NONE and save vdb.
And dynamic vdb (save vdb as XML file) doesn't contain this element either.
> There isn't a way to set the Connection type on a VDB in the Designer
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-3087
> URL: https://issues.jboss.org/browse/TEIIDDES-3087
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 11.0.1
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 11.1
>
>
> Because of https://issues.jboss.org/browse/TEIID-4957 a customer would need to be able to set the Connection Type on a VDB in the Designer before deploying it. There currently is not a way to do that. You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months