Bug 126408

Description:
Loading a test database in LO 6.3.0.1, I am asked:
"The document contains embedded HSQL data, which is deprecated. Would you like to migrate to Firebird now?" 
However, answering "Yes" leaves me with corrupted data.

Test case: attachment 135786 [details] (originally created for bug 112023). This small sample base contains these data:

    MyTimestamp            MyDouble
    01-01-2015 00:00:01    1.2345
    01-01-2015 00:00:15    3.1415

which in standard formatting are shown like

    MyTimestamp            MyDouble
    01-01-15 00:00         1.23
    01-01-15 00:00         3.14

Opening the sample database in LO 6.2.5.2, or answering "Later" to migration, this is how the data appear.

However, answering "Yes" to migration, the time data are shifted one hour, and the decimal data are completely corrupted:

    MyTimestamp            MyDouble
    31-12-14 23:00         0
    31-12-14 23:00         1.10E+227


Steps to Reproduce:
1. Open the sample database in LO 6.3.0.1 (or earlier 6.3.0.x)
2. Click on "Tables", answer "Later" to migration
3. Open Table1 - data are correct (as described above)
4. Close database
5. Re-open sample database, click on "Tables" and answer "Yes" to migration
6. Open Table 1 and notice corrupted data

Actual Results:
After migration, timestamps are shifted by 1 hour and numeric data are corrupted.

Expected Results:
After migration, all data should be as originally.


Reproducible: Always


User Profile Reset: No



Additional Info:
The link https://wiki.documentfoundation.org/Documentation/HowTo/MigrateFromHSQLDB confirms that migration is buggy, including the bug that shifts timestamps by 1 or 2 hours. If this is known to be buggy, it seems to early to deprecate the HSQL. If buggy migration is kept, then a lot of Base users are likely going to lose data and lose confidence in Base.

Migration problem found with version 6.3.0.1:

Version: 6.3.0.1 (x64)
Build ID: 41ac97386aba908b6db860cfb4cfe2da871886ae
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; 
Locale: da-DK (da_DK); UI-Language: en-GB
Calc: C

Tested in 6.3.0.0.Alpha1 with similar results.
Current "fresh" version 6.2.5.2 does not suggest migration and accordingly works fine.