Re: [sqlite] [BugReport]Data changes cannot actually flush to disk

2016-06-08 Thread r . a . nagy
Some times writes that have been cached will not be written to disk. In code we use the flush() to insure changes are made. In the OS we need to be sure that the system has been shutdown properly. .02 ends. Sent from my iPhone > On Jun 8, 2016, at 7:20 AM, Simon Slavin wrote: > > >> On 7 J

Re: [sqlite] [BugReport]Data changes cannot actually flush to disk

2016-06-08 Thread Simon Slavin
On 7 Jun 2016, at 8:13am, 刘翔 wrote: > Problem: > When update database and power off immediately, How soon do you turn the power off ? Two seconds ? Ten seconds ? One minute ? What type of hard disk do you have ? Is it a rotating disk or a solid state drive ? Is the drive you have the dat

Re: [sqlite] [BugReport]Data changes cannot actually flush to disk

2016-06-08 Thread Richard Hipp
On 6/7/16, 刘翔 wrote: > Dear SQLite developers, > > Sqlite version: 3.8.8.3 > Linux version: 3.10.31-ltsi > > Problem: > When update database and power off immediately, it cannnot actually make > changes to database file in the disk. > Although the HAVE_FDATASYNC comile-time option is true. > If ma

[sqlite] [BugReport]Data changes cannot actually flush to disk

2016-06-07 Thread 刘翔
Dear SQLite developers, Sqlite version: 3.8.8.3 Linux version: 3.10.31-ltsi Problem: When update database and power off immediately, it cannnot actually make changes to database file in the disk. Although the HAVE_FDATASYNC comile-time option is true. If manually called sync() after executing