On unix, you should usually only get SQLITE_IOERR_WRITE if write() returns -1 for some reason other than ENOSPC - in other words, if the write failed for some reason other than the disk being full.
On Mon, Nov 21, 2011 at 4:05 AM, Tal Tabakman <tal.tabak...@gmail.com>wrote: > As a continuation to the bellow: > I am using linux RH5 > "uname -a" on my machine gives: > Linux vl-talt 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 > x86_64 x86_64 GNU/Linux > > > On Sun, Nov 20, 2011 at 6:53 AM, Tal Tabakman <tal.tabakman at > gmail.com <http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > >>wrote: > > >* in a continuation to the below, it seems I get the following extended > err*>* code*>* SQLITE_IOERR_WRITE*>* what are the reasons for that one ? is > it a symptom of mem blow-up ?*>* cheers*>* Tal*>**>**What operating system > did you say you were using? > > > >* >* Hi Guys,*>* in which cases can I get sqlite3 error "disk I/O error", > is*>* it only when*>* disk is full ?*>* any other reasons for getting this > one*>* ?*>***>* Lots of reasons. Use sqlite3_extended_errcode() to get a > more detailed*>* error code that can help isolate the problem. And/or > use*>* sqlite3_config(SQLITE_CONFIG_LOG,...) to register a callback > function that*>* will give more detailed error messages.*>* > _______________________________________________* > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
