Ahhh yeah, that definitely sounds like the kind of thing that could happen.

Thanks for reporting it @AO-StreetArt. 😄

In addition, I wanna say, when copying NULL field and inserting it in another cell just inserts NULL as text.

@innermous Awesome! 😁

I've just reopened this because before we close stuff, we always ask the person who created the bug report to confirm it first. That's because even though most of the time things are ok, sometimes fixes turn out to be not-quite-as-complete as we were expecting. Or the bug reporter finds an unexpected side effect. 😉 So asking the bug reporter to verify things first leads to a better result.

@AO-StreetArt Would you be ok to try the latest nightly build (download locations are on the front page of our project) and let us know if it's working properly for you now? 😄

@AO-StreetArt Ping?

Sorry for the delayed response, absolutely ill test it at work tomorrow when I use the browser :)

I have re-tested the issue with the latest nightly build and the crash is no longer observed.

I tested copying a blank value into a populated cell, copying a blank value into a blank cell, copying a blank value into a null cell, and copying blank values into cells with different data types. All tests passed.

Note: It is interesting that the Browse Data tab doesn't perform validations on entries into the cells based on data type. Was this intentional?

Closing this ticket, thank you for the quick response!

Awesome, thanks heaps for testing it and getting back to us @AO-StreetArt. 😄

@AO-StreetArt Just noticed your question about no validation of entries based on data type.

Just in case you're still curious about it, yeah, this is intentional. 😉

SQLite itself considers the flexibility of datatypes to be a feature, and we'd be opening a weird can of worms if we didn't follow with the official position with it. 😄

    https://www.sqlite.org/datatype3.html

Hope that helps. 😄

Very good explanation!