Hello, I’m using SQLite to construct an updatable dataset (a rather large one, with 10M+ rows). I’m repeatedly issuing `INSERT … ON CONFLICT DO UPDATE` statements, adding a few thousand tuples at a time. This is OK when I just need to update the dataset with new data, but slow when constructing the dataset from scratch. Understandably so: the index has to be continuously updated, as it’s possible that each new row can conflict with already existing ones. I think this yields a runtime of O(n^2 log n), where n is the number of inserted rows. However, in the create-from-scratch scenario, I can guarantee that there will be no conflicts. Now, I _could_ change my code to generate plain `INSERT` statements without an index in the creation mode (and only create the index at the end of the process), but I’m wondering whether I could have my cake and eat it too (by not introducing modality). I envision a directive that would tell SQLite to “stop updating index until the time comes to commit the transaction, at which point do it in one go.” Does SQLite have anything like this? Is it possible to get this behaviour while using SQLite as is? Thanks, –Daniel