Unexpected affect of COMPUTED-BY value on results in some cases
---------------------------------------------------------------
Key: CORE-5097
URL: http://tracker.firebirdsql.org/browse/CORE-5097
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0 RC1
Reporter: Pavel Zotov
Samples from CORE-5092 (new ticket was created as Adriano suggested):
Sample-1.
========
SQL> recreate table test(
CON> t0 timestamp default 'now'
CON> ,t1 timestamp computed by( 'now' ) ---------------- ::: NB ::: 't1' has
EXPLICITLY defined type: TIMESTAMP
CON> ,t2 computed by( extract(day from t1) ) ------------ Should TIMESTAMP type
of 't1' be seen from here ?
CON> );
SQL> insert into test default values;
SQL> set list on;
SQL> select t0, t1 from test;
T0 2016-02-01 16:21:00.2210
T1 2016-02-01 16:21:00.2210
SQL> select t0, t1, t2 from test;
Statement failed, SQLSTATE = 42000
expression evaluation not supported
-Invalid argument for EXTRACT() not being of DATE/TIME/TIMESTAMP type
SQL>
Sample-2
========
create table t1 (n1 integer, c1 integer computed by (1.2));
insert into t1 values (0);
commit;
select * from t1;
N1 C1
============ ============
0 1
select c1 || '' from t1;
CONCATENATION
=============
1.2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel