#10636: "Execute Bind” for DB2 8.2 - current time not used, a hard coded date in 2005 is used instead

swissarmyknife(*) reported 2013-10-29T22:52:42Z · last modified 2013-10-30T22:01:43Z

Dev	ivangron
QA	tariqrahiman

Priority	Low
Complexity	Unknown

Component	Script Object
Version	14.0

Version: 14.0.3-7

Build #: 34592

Build Date: 2013-Oct-29 11:19:41 AM

1. Execute Bind on the TIME_BUG stored procedure in DB2 LUW 10.1 on 10.168.11.59

2. Notice the .variable P_CURRENT_TIMESTAMP, TIMESTAMP, '2005-01-01 12:00:00'

3. this should be using the current time, not a date from 2005.

see attached

All Comments (7) Change History

SachinPrakash 2013-10-29T22:57:01Z

AFTableColumnInfo.getDefaultValueForClassTypeAsString

swissarmyknife(*) 2013-10-29T23:02:32Z

do note that title of the issue refers to DB2 8.2, but I see this in more recent versions of DB2 LUW, such as DB2 v10.1.0.872.

ivangron 2013-10-30T17:09:16Z

Default Date, Time & DateTime will now be based off the current client machines datatime.

tariqrahiman 2013-10-30T19:52:48Z · (edited)

There is an extra ' that is getting generated for TIME datatype which you have introduced in execute bind. This does not occur in ADS 13.0

swissarmyknife(*) 2013-10-30T19:56:29Z

To find an example of this extra single quote on the TIME datatype look into

DB2 v10.1 on 10.168.11.59:50000 as db2admin SAMPLE database

the My Schema > Stored Procedures > TIME stored procedure

ivangron 2013-10-30T20:23:27Z

fixed

tariqrahiman 2013-10-30T22:01:43Z

Resolved in 14.0.3-12