https://bugs.kde.org/show_bug.cgi?id=365469
Jarosław Staniek <stan...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|2.9.7 |3.0 Alpha
--- Comment #1 from Jarosław Staniek <stan...@kde.org> ---
Thanks Juan!
It helped that you pasted the error message. I found out the reason.
The scenario is as follows:
- you inserted a field with integer type and set UNSIGNED property true for it
- then you changed that type to TEXT (in general any type that does not support
UNSIGNED property)
- upon table creation Kexi adds the UNSIGNED specifier when it's illegal in
such case; that's a bug in Kexi
In the case you mentioned the filed name is 'document'. There may be more
fields like that, you will find this while saving the design.
Current workaround:
- temporarily change the type of the problematic field back to integer
- UNSIGNED property will re-appear; set the UNSIGNED property to FALSE
- change the type back to the desired type
- do all the above 3 steps for any other type that has the same problem; to see
if you're done just try to save the design
--
You are receiving this mail because:
You are watching all bug changes.
