2018/07/09 17:48:10 [Flush] unable to open database file 2018/07/09 17:48:12 [Flush] unable to open database file 2018/07/09 17:48:17 [Flush] unable to open database file 2018/07/09 17:48:18 [Flush] unable to open database file 2018/07/09 17:48:19 [Flush] unable to open database file 2018/07/09 17:48:24 [Flush] unable to open database file 2018/07/09 17:48:25 [Flush] unable to open database file 2018/07/09 17:48:26 [Flush] unable to open database file 2018/07/09 17:48:32 [Flush] unable to open database file 2018/07/09 17:48:33 [Flush] unable to open database file 2018/07/09 17:48:38 [Flush] unable to open database file 2018/07/09 17:48:39 [Flush] unable to open database file 2018/07/09 17:48:40 [Flush] unable to open database file 2018/07/09 17:48:45 [Flush] unable to open database file 2018/07/09 17:48:46 [Flush] unable to open database file 2018/07/09 17:48:47 [Flush] unable to open database file 2018/07/09 17:48:52 [Flush] unable to open database file 2018/07/09 17:48:53 [Flush] unable to open database file 2018/07/09 17:48:54 [Flush] unable to open database file 2018/07/09 17:48:57 [Flush] unable to open database file
Inventors quantify - small dreamsWhat's up? Open a database connect with both query and update (different statements, regardless of order) and do not close after execution. This will generate a temporary file with an extension called s3db-journal. If you run the update using this connect again, you will get the exception of the unable to open database file string. So, after a connect is executed, it either closes or processes the temporary file itself. What's up? This may be the reason. Is it easy to download the code?
Inventors quantify - small dreamsThat's not very nice.
George, please.Thank you very much. The problem has been solved, the reason being that my host server is full of disk space.