--- [EMAIL PROTECTED] wrote:
> Your approach only works in simple cases. The number of changes is a
> connection/sqlite3* wide number - ie any SQLite statements associated with it
> can cause changes. This would certainly be the case when multi-threading is
> used.
Yes, agreed
> Even in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edzard Pasma wrote:
> It appears satisfactory so far. Still wonder why a work-around like this is
> needed.
Your approach only works in simple cases. The number of changes is a
connection/sqlite3* wide number - ie any SQLite statements associated
ike this is
needed.
Edzard Pasma
--- [EMAIL PROTECTED] wrote:
From: "Edzard Pasma" <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Subject: [sqlite] reporting number of changes
Date: Tue, 9 Dec 2008 01:36:39 -0800
Hello,
The API function sqlite_changes reports the number of
Hello,
The API function sqlite_changes reports the number of rows changed in the last
update/insert/delete. I'd like to use this in a generic SQL-tracing tool and
find it a bit inconvenient as the value can only be used if the statement was
an update/insert/delete. Is there a reason that the
4 matches
Mail list logo
