[Libreoffice-bugs] [Bug 132814] New: EDITING: Impossible to change an existing Integer primarykey in MySQL/MariaDB to AutoValue in GUI
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Thu May 7 13:23:26 UTC 2020
https://bugs.documentfoundation.org/show_bug.cgi?id=132814
Bug ID: 132814
Summary: EDITING: Impossible to change an existing Integer
primarykey in MySQL/MariaDB to AutoValue in GUI
Product: LibreOffice
Version: 6.4.3.2 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Base
Assignee: libreoffice-bugs at lists.freedesktop.org
Reporter: robert at familiegrosskopf.de
Use a MariaDB or MySQL-database for this bug.
Connection through ODBC, JDBC or direct driver give the same result.
Create a table in the GUI, two fields:
ID > INTEGER
name > VARCHAR(50)
Set ID to primary key, but not to AutoValue.
Save the table and close the table.
Open the table to input data. AutoValue isn't created.
Open the table for editing and set ID to AutoValue.
Save the table.
At this moment the bug appears: When saving the table the AutoValue will be set
back from "Yes" to "No". You can't can't change a primarykey in a
MySQL/MariaDB-database through the GUI form AutoValue "No" to AutoValue "Yes".
No go to Tools → SQL
ALTER TABLE `table` CHANGE `ID` `ID` INT(10) NOT NULL AUTO_INCREMENT;
The ID will be changed to AutoValue without any problem.
Seems this bug has nothing to do with the connection to MySQL/MariaDB. Its an
internal problem of the GUI.
--
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/20200507/79f5a32e/attachment.htm>
More information about the Libreoffice-bugs
mailing list