Thanks again to Jerry and also to John N. Therefore, I always run RM's Rebuild Indexes tool immediately after running an SQLite script that performs inserts or deletes. But apparently RMNOCASE cannot be replicated perfectly. The RMNOCASE collating sequence can beįaked in an SQLite manager. It's almost impossible to do the Rebuild Index yourself directly from SQLite because of RM's strange and proprietary collating sequence called RMNOCASE. Indexes tool will fix the problem as you have already discovered. This behavior is not in accord with my understanding of how SQL databases are supposed to work, but the problem is probably with me and not with the SQL databases. For reasons I don't fully understand, such deletes sometimes mess up theÄatabase level indexes on the table from which the deletes were done. The errors when you run the Test Database Integrity tool in RM after deleting the SourceID=0 citations is unfortunately normal and expected behavior when running deletes from SQLite. But other than that, the best thing to do is to get rid of the invalid citations. To see if I could figure out what was supposed to be there. The only thing I might do first would be to go to a few of the SourceID=0 citations in the RM user interface You are going to lose them, but they are already lost and getting rid of them is the goal. I think you are ok deleting the SourceID=0 citations. The RMNOCASE collating sequence can be faked in an SQLite manager. In any case, RM's Rebuild Indexes tool will fix the problem as you have already discovered. For reasons I don't fully understand, such deletes sometimes mess up the database level indexes on the table from which the deletes were done. The only thing I might do first would be to go to a few of the SourceID=0 citations in the RM user interface to see if I could figure out what was supposed to be there.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |