[
https://issues.jboss.org/browse/TEIIDDES-768?page=com.atlassian.jira.plug...
]
Paul Nittel commented on TEIIDDES-768:
--------------------------------------
Yes, the evil behavior I'd seen when I wrote this up has been corrected. I tried both
the Criteria and Expression builders and both placed their results in the transformation
SQL in the correct location!
Criteria Builder may insert crieria inside object names if user not
careful
---------------------------------------------------------------------------
Key: TEIIDDES-768
URL:
https://issues.jboss.org/browse/TEIIDDES-768
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 7.1.1
Environment: JBDS 4.0 Beta2
Reporter: Paul Nittel
Assignee: Dan Florian
Fix For: 7.4
I start with:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT * FROM PartsSource.PARTS;
END
At this point the Criteria Builder (and Expression Builder) button is disabled. So I
click in the SELECT clause to enable the button. Let's say I click between the P and
the A of .PARTS. The button enables, I craft my WHERE clause, click OK and wind up with:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT * FROM PartsSource.PA WHERE PartsSource.PARTS.PART_COLOR =
PartsView.getPartsByColor.colorInRTS;
END
Regardless of where in the SELECT I click, the WHERE clause should be inserted in a
syntactically correct location.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira