Timestamp format in Data Compare wrong
Timestamp format in Data Compare wrong
I am using the dbforge Data Compare for Oracle tool to generate scripts for our DBA group. all of our date fields use a TIMESTAMP data type so when I generate a script through Synchronization I would expect the output in the file to match the yyyy-MM-dd hh:mm:ss.ffffff format set under Tools/Options/Data Editor/Formatting/Timestamp. The file instead contains a date in the format of MM/dd/yyyy hh:mm:ss.ffffff. Where is this being declared for the script file being generated through Synchronization?
Re: Timestamp format in Data Compare wrong
We will review this and will answer you as soon as possible.
Re: Timestamp format in Data Compare wrong
Are there any updates on this issue?
Re: Timestamp format in Data Compare wrong
Hello,
The settings you are talking about are tied with a data mapping in Data Editor.
A synchronization script is being created considering settings set during the session.
Please pay attention to the following parameters within a synchronization file.
ALTER SESSION SET NLS_TIMESTAMP_FORMAT = 'SYYYY/MM/DD HH24:MI:SS.FF';
ALTER SESSION SET NLS_TIMESTAMP_TZ_FORMAT = 'SYYYY/MM/DD HH24:MI:SS.FF TZH:TZM';
The settings you are talking about are tied with a data mapping in Data Editor.
A synchronization script is being created considering settings set during the session.
Please pay attention to the following parameters within a synchronization file.
ALTER SESSION SET NLS_TIMESTAMP_FORMAT = 'SYYYY/MM/DD HH24:MI:SS.FF';
ALTER SESSION SET NLS_TIMESTAMP_TZ_FORMAT = 'SYYYY/MM/DD HH24:MI:SS.FF TZH:TZM';
Re: Timestamp format in Data Compare wrong
So where is the Data Compare tool determining what to populate the alter session statements at the top of the file with? Is there a way I can control what the template will look like?
Re: Timestamp format in Data Compare wrong
Unfortunately, there is no a possibility to control these settings except on changing the settings directly in the sync script.
Though, we will review implementing such a possibility when developing the next product versions.
Though, we will review implementing such a possibility when developing the next product versions.