Devart Forums

Hello,
I'm comparing data from a distant MySQL database and my machine where I keep a copy for application development.
When comparing DateTime columns, the comparison founds thousands of difference where the source value is 01.01.0001 00:00:00 and the destination value is 0000-00-00 00:00:00. Even after synchronization, the same differences are still there. If I don't make a mistake, the value in the MySQL table is the same and it's just the text representation that differs (not the same MySQL version).
Under version 5 of dbForge, I never see these differences.
Is it a bug?
If true, you should correct it, otherwise, please add an option to treat these dates as not different.
Patrick

After performing the synchronization, could you please provide us a screenshot displaying the fact that the records appear under the 'Different Records' tab? Please make sure you are starting a new data comparison (a new .dcomp document is generated) after the previously performed synchronization?

You can send the reply straight to our support system at supportATdevartDOTcom, so we will keep further correspondence with you on this issue via that system.

Could you please provide us the versions of the Source and Target servers by executing the following query on both the servers:

SELECT @@version

Hello Alexa,
source server: 5.1.50-community
target server: 5.5.28
Patrick

Unfortunately, we still were not able to reproduce the issue.

Could you please also confirm that you are using the latest build 6.0.151 of dbForge Studio for MySQL: http://www.devart.com/dbforge/mysql/stu ... nload.html

Please also provide us the options you're selecting on the 'Options' page of the 'New Data Comparison' wizard.

Hello Alexa,
yes I'm using version 6.0.151.
I'm never had this problem with version 5.x, it starts with version 6.0.
Patrick

Could you please also provide us the options you're selecting on the 'Options' page of the 'New Data Comparison' wizard?

Hello Alexa,
after exporting:

/datacompare

/source connection:"xxx"
/target connection:"yyy"
/MappingIgnoreSpaces:Yes
/IgnoreBlobColumns:No
/MappingIgnoreCase:No
/MappingIgnoreUnderscores:No
/IgnoreColumnsByMask:No
/ExcludeObjectsByMask:No
/IncludeObjectsByMask:No
/CompareTables:Yes
/CompareViews:No
/RoundFloatTypes:No
/IgnoreTrailingSpaces:No
/IgnoreCase:No
/IsEmptyStringEqualsNull:No
/IsIgnoreTime:No
/CheckDifferent:Yes
/CheckOnlyInSource:Yes
/CheckOnlyInTarget:Yes
/CheckIdentical:No
/DisableForeignKeys:Yes
/DisableDmlTriggers:Yes
/DisableObjectKeys:No
/ExcludeComments:No
/UseCommitMode:No

Patrick

Thank you for the reply.

Could you please help us some more in investigating this issue and perform the following:

1. The CREATE TABLE statements of the Source and Target tables containing the DateTime columns (right-click the table in Database Explorer and select 'Generate Script As -> CREATE' from the popup menu).
2. Please provide us the synchronization script for the table.
3. Select 'Tools -> Options' from the main menu. The 'Options' window opens.
4. Navigate to the 'Environment -> Output' branch.
5. Select the 'Turn on "Redirect Data to Output window" by default' option.
6. Execute some SELECT statement returning a few records that appear to be different against each table and provide us the results from the 'Output' window (select 'View -> Output' from the main menu).

We would like to let you know that the new build 6.0.265 of dbForge Studio for MySQL, where the issue you reported is fixed, has been released and is available for downloading: http://www.devart.com/dbforge/mysql/stu ... nload.html

Thank you for your help in improving dbForge Studio for MySQL.

Hello Alexa,
thanks for the fix, it works perfeclty now, after the first update.
Patrick