On 2019/02/18 1:02 PM, Dominique Devienne wrote:
On Mon, Feb 18, 2019 at 11:48 AM R Smith <ryansmit...@gmail.com> wrote:
Note that in a transaction without WAL mode ... your query may or may not
"see" data that is older,
Hmmm, I don't think so. Journal mode, WAL or not, doesn't matter.
If you are inside a transaction, you are inside it. And will see the
current rows for that TX,
whether you are inside the outer query, or the "inner" one (inside the
UDF). --DD
Thank you for saying Dominique, this is important. I neglected to state
that it is inside another transaction, not it's own transaction.
To be clear, and to check if I do not have it wrong perhaps, let me ask
here: If I start a new SELECT query (whether inside a UDF or not), while
another transaction is going on in a DB with WAL and read_uncommitted
set - can I or can I not "see" data changed by that transaction but not
yet committed?
If not, I apologize, and is very interested in where then
"read_uncommitted" becomes useful?
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
