[sqlite] Fwd: sqlite3_busy_timeout() on NetBSD

Tobias Rundström Mon, 03 Jul 2006 13:28:48 -0700

Hello List,

Got this email from this a developer of XMMS2 Sounds a bit scary,anyone have seen this before?


-- Tobias

Begin forwarded message:

From: Alexander Botero-Lowry <[EMAIL PROTECTED]>
Date: måndag 3 jul 2006 16.13.29 GMT-04:00
To: [EMAIL PROTECTED]
Subject: Fw: sqlite3_busy_timeout() on NetBSD

Begin forwarded message:

Date: Sun, 2 Jul 2006 15:34:40 -0500
From: Alexander Botero-Lowry <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Subject: sqlite3_busy_timeout() on NetBSD

Hi,

I'm an xmms2 developer who does most of the work of getting xmms2
working on the various BSDs. I've currently run into a strange problem
with sqlite3_busy_timeout on NetBSD. It seems that it doesn't timeout
at all. Though sqlite3_busy_timeout() is set to 60000, when:

sqlite3_exec (sql, "PRAGMA user_version",
                              xmms_sqlite_version_cb, &version, NULL)

is called, we immediately get back SQLITE_BUSY instead of having it

wait for the lock to end. I was able to very very hackishly workaround

this problem with:

               if (sqlite3_exec (sql, "PRAGMA user_version",
                              xmms_sqlite_version_cb, &version, NULL)
== SQLITE_ BUSY) {
                                xmms_log_debug("busy...");
                                sleep(1);

sqlite3_exec(sql, "PRAGMAuser_version",xmms_sqlite_version_cb, &version,NULL);

                }

Obviously this isn't a real solution, but it does solve the problem...

Is there something wrong with sqlite3_bus_timeout on NetBSD?

One can find the more complete source of out sqlite wrapper at:

http://git.xmms.se/?p=xmms2-devel.git;a=blob;h=d0ee1489ad19aba2a4b72e569effd143417bcdda;hb=6732ab998047e684a99e558c99edb62466511df8;f=src/xmms/sqlite.c


Thanks in advance, Alex

Please CC, off list.

!DSPAM:44a97a9f190355315134984!

[sqlite] Fwd: sqlite3_busy_timeout() on NetBSD

Reply via email to