On 7 Aug 2011, at 9:45pm, skywind mailing lists wrote: > It only happens when the iPhone/iPad is running out of batteries (perhaps > during a write operation?).
Out-of-battery-power detection on an iPhone happens quite early. While there's still plenty of life left, all applications get 'you are being backgrounded' notification. Once each one has responded to this (or if it was already in the background) it gets a 'you are being quit' notification. Once they've all responded to this, the phone actually shuts down. If an application does not respond to one of the notifications in a reasonable time, then the OS will force-quit it. But that's rare: you'd almost certainly realise things were going wrong during testing. On 7 Aug 2011, at 9:53pm, skywind mailing lists wrote: > why is the database corrupted when sqlite3_close() is not called? I thought > that I might lose data but the database is actually corrupted and not > accessible anymore! > > Can you explain what happens? I'm sorry but I can't. But SQLite is designed to need sqlite3_close() (and, in fact, sqlite3_shutdown()) so it's probably best to do them. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
