On 4/12/19, Jim Dossey <[email protected]> wrote: > I'm doing the INSERT first, without a BEGIN ... COMMIT transaction, then I'm > doing the SELECT. Shouldn't the INSERT do it's own COMMIT which should make > the new row visible to the SELECT? Should I add a BEGIN ... COMMIT around > the INSERT?
Perhaps the SELECT is running inside of a transaction that was started before you did the INSERT. For example, perhaps you didn't sqlite3_finalize() the previous SELECT, which caused it to hold the read transaction open. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
