Page 1 of 1
CreationTime and LastUpdated in local time instead UTC in InstanceTable
Posted: Fri 07 Nov 2014 09:43
by m.weber.insiders
Hi.
I'm using dotConnect for Oracle to persist workflows.
I have the problem, that the dates in CREATIONTIME and LASTUPDATED are in local time instead of UTC.
Any ideas how to solve this problem?
Thanks for your help.
Greetings
Re: CreationTime and LastUpdated in local time instead UTC in InstanceTable
Posted: Fri 07 Nov 2014 17:13
by Shalex
Thank you for your report. We will update the \WF Services\OracleInstanceStoreLogic.sql and \WF Services\NET45\OracleInstanceStoreLogic45.sql scripts which are provided with dotConnect for Oracle installation to store UTC instead of local time and notify you.
Re: CreationTime and LastUpdated in local time instead UTC in InstanceTable
Posted: Wed 12 Nov 2014 09:58
by m.weber.insiders
Hi.
Do you have an idea, when this issue is going to be fixed? A customer is waiting for this fix.
Greetings
Re: CreationTime and LastUpdated in local time instead UTC in InstanceTable
Posted: Wed 12 Nov 2014 11:39
by MariiaI
m.weber.insiders wrote:Hi.
Do you have an idea, when this issue is going to be fixed? A customer is waiting for this fix.
Greetings
We have fixed this issue. The fix will be included in the next public build of dotConnect for Oracle, which we plan to release in about 1-2 weeks. We will inform you when it is available for download.
Re: CreationTime and LastUpdated in local time instead UTC in InstanceTable
Posted: Thu 20 Nov 2014 17:29
by Shalex
The behaviour is changed in the new (8.4.293) build of dotConnect for Oracle: SYS_EXTRACT_UTC(SYSTIMESTAMP) is used now in WF Services scripts for the date columns.