Summary: | Field add corrupts table | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | walkerkorea |
Component: | Database | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | major | ||
Priority: | medium | CC: | dr, iplaw67, LibreOffice, robert, suokunlong |
Version: | Inherited From OOo | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=71224 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Database shows table before and after relocate columns by GUI
Describes, how to reproduce the bug. |
Description
walkerkorea
2012-06-30 13:37:00 UTC
You can not sort the columns while editing the table in the GUI. If you will change a table and put C at the place you wish, this would only work with a SQL-command in the HSQLDB: ALTER TABLE "X" ADD "C" VARCHAR(25) BEFORE "D"; The changes in the table were made, when you save the table. So when you cut "D" and put "C" at this position it is recognized as a renaming of the column. In the HSQLDB there is no possibility to cut and paste a column. Hi reporter, IMHO your observation isnĀ“t a bug. Okay? Created attachment 73473 [details]
Database shows table before and after relocate columns by GUI
Created attachment 73474 [details]
Describes, how to reproduce the bug.
There is a possibility to cut and paste fields in the table-editor of the Base-GUI. Users might think, that it would cut and paste the whole content of the field (the whole column). But this function cuts and pastes only the name and the type of the field. So the old contend appears at another position of the table. In the example-database a field of a birthday (DATE) is changed to a field of a street (VARCHAR) - the date of the birthday appears as varchar in the street-column.
The behavior is the same on Windows and other platforms. This bug exists since the first version of LO. Changed the bug to New. Adding self to CC if not already on |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.