[
https://issues.jboss.org/browse/TEIID-5290?page=com.atlassian.jira.plugin...
]
dalex dalex commented on TEIID-5290:
------------------------------------
1. add a switch to turn on the old function implementation
2. create a new determinism level between command and non-deterministic that goes down to
the procedure statement level.
good options, hm, I even don't know which one
will be better. The first option can be implemented very quickly but from another point of
view we should explicitly turn it on or off. What do you think as well? Maybe the second
option better? Or it will take much time?
NOW() function returns the same value for each call in BEGIN...END
block
------------------------------------------------------------------------
Key: TEIID-5290
URL:
https://issues.jboss.org/browse/TEIID-5290
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 10.1
Environment: teiid-10.1.0 on WildFly Full 11.0.0.Final (WildFly Core
3.0.8.Final)
Reporter: dalex dalex
Assignee: Steven Hawkins
Fix For: 10.2
Run the following queries:
{code:sql}
BEGIN
declare timestamp ts1 = select now();
DECLARE integer c = 20000;
WHILE (c > 0)
BEGIN
c= c-1;
END
declare timestamp ts2 = select now();
select ts1, ts2;
END ;;
{code}
and
{code:sql}
BEGIN
DECLARE integer c = 20000;
create local temporary table #tem(ts timestamp);
WHILE (c > 0)
BEGIN
INSERT INTO #tem VALUES((select NOW()));
c= c-1;
END
select * from #tem;
END ;;
{code}
NOW() function returns the same value for each call in BEGIN...END block and it
doesn't matter if it is atomic or not.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)