Version: 2.4 alpha3 (Calligra 2.4 alpha3) (using KDE 4.6.0) OS: Linux Trying to set a non integer field to primary key results in the field's type to be changed to integer without a warning. That COULD LEAD TO DATA LOSS! Reproducible: Always Steps to Reproduce: Open a table at design view. Select a field with a data type other than integer. Click to make it primary key. Actual Results: The field's type is converted to integer without any warning. Saving the table could lead to data loss. Expected Results: The user should be prompted that only an integer field is accepted as a primary key, and let the user change the type himself if he wanted. When a different type could be allowed to be a primary key, the message should be changed accordingly.
Thanks, non-intrusive warning is a good idea. That said, some databases have good support for text types as primary keys...
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.