[ https://issues.jboss.org/browse/TEIID-5290?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-5290: ------------------------------------ I indeed checked it on PostgreSQL and it has the same behavior as in teiid, that is as a deterministic value. Actually I suspected that behavior will be like a deterministic value and I've already encountered with it in scope of the TEIID-4423 issue. But there we agreed about such behavior: "So now: update test.textagg_test_2 set id =(select uuid()) where id = 'xxxx'; will evaluate to a single id value. update test.textagg_test_2 set id =uuid() where id = 'xxxx'; will set an id per row, which in this case without a key will result in an error." What do you think can we do the same here? For example, if we use explicitly the "select now()" then it should be treated as a deterministic value but if we use just now() function, say, like here: {code:sql} BEGIN declare timestamp ts1 = now(); DECLARE integer c = 20000; WHILE (c > 0) BEGIN c= c-1; END declare timestamp ts2 = now(); select ts1, ts2; END ;; {code} it will be treated as a non-deterministic value. -- This message was sent by Atlassian JIRA (v7.5.0#75005)