Hi, We noticed that an assertion is converted back to a conditional in this check in(https://www.sqlite.org/src/info/4d0b9109f7a5312d4e136395e08b11dad64d746bc106ad44d47675e5b1dcb4ef <https://www.sqlite.org/src/info/4d0b9109f7a5312d4e136395e08b11dad64d746bc106ad44d47675e5b1dcb4ef>). We are surprised that this assertion exists for over 10 years. We tried to understand why such a condition is hardto be triggered but failed due to unfamiliarity of sqlite codebase. Currently our guessing is that this will be triggers by natural join(which uses group by implicitly), a table with primary key and an IN expression. Could anyone help explain this? Thanks!
Yongheng & Rui _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users