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?
The INSERT is done with sqlite3_exec(). Do I need to call any other functions after that to make the new row visible to other connections? > On Apr 12, 2019, at 2:15 PM, Richard Hipp <d...@sqlite.org> wrote: > > On 4/12/19, Jim Dossey <jim.dos...@gmail.com> wrote: >> >> The problem is when I do an INSERT and then try to SELECT that record by >> rowid it doesn't find it. > > Yes, because the SELECT is working inside a single transaction, but > the INSERT is adding content in a separate, subsequent transaction > which the SELECT never sees. This is by design. > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
