JBossDeveloper

S.Q,

We have logged https://jira.jboss.org/browse/TEIID-1346. This is going to be fixed and be part of the 7.2 release that is coming up.

Thanks.

Ramesh..

S.Q,

SteveH is looking into issue logged above and has found couple other issues that may concern with full feature nature of the TRANSLATE CRITERIA.

We are investigating it. Mean while, you can workaround this issue by adding

UPDATE set foo='blah' WHERE 1=1 and TRANSLATE CRITERIA

This way it adds the required CRITERIA and behaves as you would expect.

I described the workaround incorrectly to Ramesh, you would need put a vacuous condition on the user query:

UPDATE x set foo='blah' WHERE 1=1

or in your update procedure check for no user criteria:

UPDATE y set foo='blah' WHERE NOT(HAS CRITERIA) OR TRANSLATE CRITERIA