[Libreoffice-bugs] [Bug 121553] New: Editing: Firebird: Table editor erroneously wants to change CLOB field to a BLOB field during alter table

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Tue Nov 20 14:27:15 UTC 2018


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

            Bug ID: 121553
           Summary: Editing: Firebird: Table editor erroneously wants to
                    change CLOB field to a BLOB field during alter table
           Product: LibreOffice
           Version: 6.2.0.0.beta1+
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: high
         Component: Base
          Assignee: libreoffice-bugs at lists.freedesktop.org
          Reporter: drewjensen.inbox at gmail.com

Created attachment 146837
  --> https://bugs.documentfoundation.org/attachment.cgi?id=146837&action=edit
Test file

The Firbird support in Base added CLOB to the list recently.
Using the table editor to create a CLOB field in a table works initially.
However if you attempt to alter the table structure subsequently by adding a
new column then during the ALTER TABLE process the CLOB field is first
erroneously reported as needing to be dropped and added to the back of the
table columns, but will change the type of field from CLOB to BLOB.

Steps to reproduce:
1 - download and open the attached test file.
2 - Open the table TABLE2 with the Table Editor
3 - Add a new column after Notes of any name and type
4 - Click on save changes.

Result:
User is prompted (see second attachment for screen shot) that the Notes field
can not be changed (OK) and instead should it be dropped and appended with new
format.

This is because what the application really wants to do is change the column
type to BLOB (a type that was supported with older versions of LO/Firebird when
it did not support CLOB), so if you the user answers yes it does just that
(which looses any data currently in the column for all records) and the user is
now unable to edit, insert, etc any data in the changed field. If the user is
sharp and answers no there is no harm.

Expected result:
The application adds the new column silently.

Setting this to priority 'High' because of the data loss potential.

-- 
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/20181120/2a980569/attachment.html>


More information about the Libreoffice-bugs mailing list