Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Losing data on fixing bad rows after UNIQUE constraint errors #3588

Open
warepilot opened this issue Oct 3, 2019 · 4 comments

Comments

@warepilot
Copy link

commented Oct 3, 2019

Details

After commit action I have UNIQUE constraint errors (constraint required). When I try to edit the bad row for fixing on the error column, data get vanished. On the other hand, commit process rises false positive on that constraint.

Steps to reproduce

Insert a big bunch of rows. Paste data. You may have UNIQUE constraint error as you configured for the table whenever you commit. Try to edit the bad row on cell related to that constraint (a STRING type). Data will vanish. I think all that happens when the pasted string is really long, but it happens with BLOB as well.

Versions

3.2.1 on Wine

@pawelsalawa

This comment has been minimized.

Copy link
Owner

commented Oct 4, 2019

"data get vanished" <- from only the cell you tried to edit, or all pasted rows disappear?

@warepilot

This comment has been minimized.

Copy link
Author

commented Oct 4, 2019

Right. From the cell I'm trying to fix, only.

@pawelsalawa

This comment has been minimized.

Copy link
Owner

commented Oct 4, 2019

I see. Okay, I think I know what may be wrong with it. It looks like the flag "limited preload" is incorrectly set to true upon pasting and when you try to edit it, application tries to "load full value" from DB, so you edit full value (not shortened, view-only value), which is not there yet and results in loading empty value. I'm writing it down here to catch-up quickly with it when I sit down to it.

@pawelsalawa pawelsalawa added the bug label Oct 4, 2019
@pawelsalawa pawelsalawa added this to the 3.2.2 milestone Oct 4, 2019
@rkoe

This comment has been minimized.

Copy link

commented Oct 12, 2019

This not only happens when pasting large data, but also when manually entering data (one or a few rows) into SQLiteStudio.
So, to be sure that no data is lost, you currently have to manually reload the table-data after every error-message, check if some values are missing, and enter them again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.