FMDB executeUpdate DROP command does halt the app?

I had the same issue, and got it solved by calling closeOpenResultSets on the FMDB instance just before the update, just like TRD said (though I didn't have to close and reopen the database completely).

I finally got rid of this nasty behaviour. I closed the database connection right before the drop query and reopened it immediately. If I have to guess I'd say that SELECT-Queries in earlier parts of my source code made the connection to be locked for DROP-statements.

So closing the database connection and reopen it resets those locks. Hope this can help you @JLoewy.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.