I was just reading through this issue: https://www.sqlite.org/src/info/343634942dd54ab
Does this bug have any other symptoms other than as specified in the report above? Reason I'm asking is that we are facing quite a bit of database corruption right now. We use a lot of expression indexes (written in custom C++ code), which now sounds suspicious. However, what we see doesn't generally exhibit like the bug describes. The bug as reported gives errors like this: "row 1 missing from index idx1" Where we instead see things like: "database disk image is malformed" Can it still be related to the same issue? In general, is there anything dangerous that you can do in a custom function inside an indexed expression that we need to watch out for? Most of the time when the database gets corrupted, we don't crash, it corrupts midway through valid SQL (no pattern to it - completely unrelated SQL). I was thinking if the expression functions have bugs in them it could cause corruption, but can't really imagine how. We use sqlite3_result_* functions to report results, and even if we read invalid memory or pass invalid memory to SQLITE, it should crash - not corrupt. - Deon _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
