Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Losing data on fixing bad rows after UNIQUE constraint errors #3588
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.
3.2.1 on Wine
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.
This not only happens when pasting large data, but also when manually entering data (one or a few rows) into SQLiteStudio.