[Libreoffice-bugs] [Bug 117106] New: HSQLDB -> Firebird migration

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=117106

            Bug ID: 117106
           Summary: HSQLDB -> Firebird migration
           Product: LibreOffice
           Version: 6.1.0.0.alpha0+ Master
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: critical
          Priority: medium
         Component: Base
          Assignee: libreoffice-bugs at lists.freedesktop.org
          Reporter: reisi007 at gmail.com

Based on https://bugs.documentfoundation.org/show_bug.cgi?id=116944#c42 a list
of TODO items for the transition:

As asked on the above listed bug discussion on the bug itself should be kept to
a minimum. (Where to discuss)

- Converting HSQLDB databases from HSQLDB to Firebird should not be enabled by
default in 6.1 -> Should be an experimental option.
  - Expert configuration entry should be added to force / ask / delay upgrade
   - In "RELEASE CONFIGURATION" builds default should be "delay", in others
"ask".

- After converting the ODB file there must not be the HSQLDB data in the file
anymore.
  - Ask to store in new file

- Automated tests should be created that cover the following aspects. The test
document should be a HSQLDB one as explicitly the transition to Firebird should
be tested:

- Relationships are working between tables:
 - 1:1
 - 1:n
 - n:m

- Auto increment of elements working (needs to be checked after converting)
- Other constraints on elements must work as well
  - UNIQUE / PRIMARY KEY / FOREIGN KEY / NON NULL on single field
  - UNIQUE / PRIMARY / FOREIGN KEY on group of fields
- All different index types (TODO: what index types are supported) need to be
mapped to corresponding INDEXES in Firebird
- All different types need to be checked whether a corresponding type is
available
 - Same range / order behavior
 - Incompatibilities need to be documented BEFORE deprecating HSQLDB backend to
allow people to prepare for the transition. 
- We need to discuss to what extend manually entered SQL needs to be covered
  - However, views created by the designer must work
  - Best effort approach for manually created views
- As long as the HSQLDB driver is integrated we can easily check if the result
of reports (or anything else relevant) is exactly the same compared to the
HSQLDB version.
- What to do with HSQLDB specific functions?
 - Firebird 3.0 does not support concat in select
   - Can be rewritten from "concat(A,B)" to "A || B" -> See above. How to
handle SQL.

After automated testing of some (conversion works and reports lead results /
entries can eb added) manual QA effort is needed. The timeframe to the 6.1
seems to close to tackle everything listed above. Therefore defaulting to
enabling this big feature for 6.1 is not recommended. As highlighted above
incompatible data types / SQL code has not been discussed as part of the
transition to Firebird.

TODO from QA side: Prepare 1-3+ test documents, which should be used as data
for automated tests. Ideally this should not only be new documents, but also
documents created by older LibreOffice versions

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20180419/d5f79a24/attachment-0001.html>