summaryrefslogtreecommitdiff
path: root/ext/async
diff options
context:
space:
mode:
Diffstat (limited to 'ext/async')
-rw-r--r--ext/async/README.txt8
-rw-r--r--ext/async/sqlite3async.c1
-rw-r--r--ext/async/sqlite3async.h4
3 files changed, 10 insertions, 3 deletions
diff --git a/ext/async/README.txt b/ext/async/README.txt
index 05acffe..f62fa2f 100644
--- a/ext/async/README.txt
+++ b/ext/async/README.txt
@@ -1,3 +1,10 @@
+NOTE (2012-11-29):
+
+The functionality implemented by this extension has been superseded
+by WAL-mode. This module is no longer supported or maintained. The
+code is retained for historical reference only.
+
+------------------------------------------------------------------------------
Normally, when SQLite writes to a database file, it waits until the write
operation is finished before returning control to the calling application.
@@ -161,4 +168,3 @@ the database, eliminating the bottleneck.
The functionality required of each of the above functions is described
in comments in sqlite3async.c.
-
diff --git a/ext/async/sqlite3async.c b/ext/async/sqlite3async.c
index 0814da7..4ab39ca 100644
--- a/ext/async/sqlite3async.c
+++ b/ext/async/sqlite3async.c
@@ -1510,6 +1510,7 @@ static void asyncWriterThread(void){
case ASYNC_DELETE:
ASYNC_TRACE(("DELETE %s\n", p->zBuf));
rc = pVfs->xDelete(pVfs, p->zBuf, (int)p->iOffset);
+ if( rc==SQLITE_IOERR_DELETE_NOENT ) rc = SQLITE_OK;
break;
case ASYNC_OPENEXCLUSIVE: {
diff --git a/ext/async/sqlite3async.h b/ext/async/sqlite3async.h
index 143cdc7..5b20d71 100644
--- a/ext/async/sqlite3async.h
+++ b/ext/async/sqlite3async.h
@@ -75,7 +75,7 @@ int sqlite3async_initialize(const char *zParent, int isDefault);
** On win32 platforms, this function also releases the small number of
** critical section and event objects created by sqlite3async_initialize().
*/
-void sqlite3async_shutdown();
+void sqlite3async_shutdown(void);
/*
** This function may only be called when the asynchronous IO VFS is
@@ -94,7 +94,7 @@ void sqlite3async_shutdown();
** If multiple simultaneous calls are made to sqlite3async_run() from two
** or more threads, then the calls are serialized internally.
*/
-void sqlite3async_run();
+void sqlite3async_run(void);
/*
** This function may only be called when the asynchronous IO VFS is