Re: [sqlite] transaction commit is successful despite I/O error

2012-10-25 Thread Efim Dyadkin
I was probably not quite specific. So I would like to rephrase the problem and give more details. I run a default configuration of Sqlite on Linux and I don't use WAL or anything that changes transaction behavior. A database is located on a remote file server and accessed via NFS. There is a

Re: [sqlite] transaction commit is successful despite I/O error

2012-10-20 Thread Efim Dyadkin
FP=7fff44f143a0 sqlite3_prepare, FP=7fff44f14410 sqlite3_exec, FP=7fff44f14520 Thanks, Efim Dyadkin This e-mail, including any attached files, may contain confidential and

[sqlite] transaction commit is successful despite I/O error

2012-10-18 Thread Efim Dyadkin
it: if( unlink(zPath)==(-1)) && errno!=ENOENT ){ return unixLogError(SQLITE_IOERR_DELETE, "unlink", zPath); } Can somebody please explain why "errno!=ENOENT" is required in here? Thank