[JBoss JIRA] (TEIIDDES-2889) Inconsistent errors in Problems View
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2889?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2889:
-----------------------------------
Priority: Critical (was: Major)
> Inconsistent errors in Problems View
> ------------------------------------
>
> Key: TEIIDDES-2889
> URL: https://issues.jboss.org/browse/TEIIDDES-2889
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations, Views
> Affects Versions: 10.0.1
> Reporter: stanislav kaleta
> Priority: Critical
> Attachments: ProductsInfo.wsdl, screenshot1.png, screenshot2.png
>
>
> Errors which occur in Designer (e.g. Transformation Editor) are not showed in Problems View immediately. Some of them appears after another action (e.g. rename project) or after VDB creation. On the other hand, some errors which were resolved in Designer remain present in Problems View.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIIDDES-2665) Add an option to not widen comparisons to string
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2665?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2665:
------------------------------------------
You would have to add an option and support both styles of resolving behavior.
> Add an option to not widen comparisons to string
> ------------------------------------------------
>
> Key: TEIIDDES-2665
> URL: https://issues.jboss.org/browse/TEIIDDES-2665
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 10.0.2, 9.2.1
>
>
> Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example:
> int_col = '1a'
> will effectively become cast(int_col as string) = '1a'
> Or with timestamps:
> timestamp_col = '1970-01-01'
> becomes cast(timestamp_col as string) = '1970-01-01'
> In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion.
> This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIIDDES-2665) Add an option to not widen comparisons to string
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2665?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2665:
----------------------------------------
[~shawkins] Can you clarify how this would show up in Designer? do we need to add a UI option to toggle between behaviors?
> Add an option to not widen comparisons to string
> ------------------------------------------------
>
> Key: TEIIDDES-2665
> URL: https://issues.jboss.org/browse/TEIIDDES-2665
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 10.0.2, 9.2.1
>
>
> Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example:
> int_col = '1a'
> will effectively become cast(int_col as string) = '1a'
> Or with timestamps:
> timestamp_col = '1970-01-01'
> becomes cast(timestamp_col as string) = '1970-01-01'
> In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion.
> This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIIDDES-2665) Add an option to not widen comparisons to string
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2665?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2665:
--------------------------------------
Assignee: Barry LaFond (was: Dan Florian)
> Add an option to not widen comparisons to string
> ------------------------------------------------
>
> Key: TEIIDDES-2665
> URL: https://issues.jboss.org/browse/TEIIDDES-2665
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 10.0.2, 9.2.1
>
>
> Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example:
> int_col = '1a'
> will effectively become cast(int_col as string) = '1a'
> Or with timestamps:
> timestamp_col = '1970-01-01'
> becomes cast(timestamp_col as string) = '1970-01-01'
> In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion.
> This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month