Bug 379080 - Changing Fields Types
Summary: Changing Fields Types
Status: CLOSED DUPLICATE of bug 125253
Alias: None
Product: KEXI
Classification: Applications
Component: Tables (show other bugs)
Version: 3.1.0 Alpha
Platform: Appimage Linux
: NOR major
Target Milestone: ---
Assignee: Kexi Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-04-22 11:35 UTC by Ian Whitfield
Modified: 2023-04-14 16:56 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Incorrect Field Type (15.47 KB, image/png)
2017-04-25 10:33 UTC, Ian Whitfield
Details
Error Message after Change (51.93 KB, image/png)
2017-04-25 10:34 UTC, Ian Whitfield
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Whitfield 2017-04-22 11:35:31 UTC
Changing Fields Types without the program deleting the entire Table/Database??
I seem to have been able to change the Field Type of my one Field from “Text” to “Photo” and I can now insert the picture I want and it “sticks” until I close the DB and re-open it and the photo is no longer there!!
Comment 1 Jarosław Staniek 2017-04-24 21:27:23 UTC
Are you able to reproduce the case that Kexi does not warn "Any data in this table will be removed upon design's saving!" after you change the field type to Object in a non-empty table? Maybe you would be able to attach a test database.

For empty tables Kexi does not warn, that's expected.

Unable to reproduce for Kexi 2.9.11, 3.0.2-pre, 3.1.0-alpha.

The behavior you mention would not be correct in these Kexi versions (change to Object without data removal nor loosing the saved table design after app restart).
Comment 2 Ian Whitfield 2017-04-25 10:33:48 UTC
Created attachment 105180 [details]
Incorrect Field Type
Comment 3 Ian Whitfield 2017-04-25 10:34:46 UTC
Created attachment 105181 [details]
Error Message after Change
Comment 4 Jarosław Staniek 2017-04-25 10:42:11 UTC
OK, so the "Error Message after Change" is rather warning about action that can't be undone. You've changed the field type, saved. What happened?
Comment 5 Ian Whitfield 2017-04-25 11:18:44 UTC
Don't know!!! I'm scared of losing my Database and don't want to have to do all that work again!!

I could try on the other DB as I have it on two different machines ....

OK - Just tried it. I changed a Field to a different Type and selected 'Save' and got the Error Message as reported.
I selected 'OK' and Kexi "crashed"
I re-opened Kexi and looked at the Table and ALL THE DATA HAS GONE!!
IMHO this has to be changed/modified or something!!!!!
Comment 6 Jarosław Staniek 2017-04-25 11:26:42 UTC
> I'm scared of losing my Database and don't want to have to do all 
> that work again!!

Whenever you need to test such things, just copy your kexi file to a new name and play with the copy...

And backup your work regularly.

> I selected 'OK' and Kexi "crashed"

Kexi version? We need to know if this was fixed recently.

Please note this https://forum.kde.org/viewtopic.php?f=220&t=138821#p375259


> I re-opened Kexi and looked at the Table and ALL THE DATA
> HAS GONE!! IMHO this has to be changed/modified or something!!!!!

Yes, this is in development: https://bugs.kde.org/show_bug.cgi?id=125253
Comment 7 Ian Whitfield 2017-04-25 11:38:14 UTC
I mentioned earlier - I'm running 3.1 Alpha AppImage 0324.
Comment 8 Jarosław Staniek 2017-05-02 19:40:07 UTC
Update: Universal Kexi "AppImage" for Linux - a new version from April 29 is
now linked at https://community.kde.org/Kexi/Snapshots. You can try it in your tests and give feedback if the bug is fixed.
Comment 9 Andrew Crouthamel 2018-09-28 02:41:42 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Andrew Crouthamel 2018-10-28 03:38:31 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 11 Jarosław Staniek 2018-12-15 23:16:05 UTC
Need info for new version
Comment 12 Bug Janitor Service 2018-12-30 03:44:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Jarosław Staniek 2018-12-30 13:07:58 UTC
Assuming it works in >=3.1 as all my tests confirm it. Setting as duplicate of #125253 which would improve this area.

*** This bug has been marked as a duplicate of bug 125253 ***