After I have read the documentation of sqlite3ExpirePreparedStatements, I better see how the GRDB authorizers dance is a misuse of the library.
The goal of GRDB authorizers, which is only to grab information about the statements before they are executed, is at odds with the fact that SQLite connections have a single authorizer dedicated to restricting database accesses. I understand why a change of authorizer invalidates statements. Conclusion: I should use a single authorizer and never change it. This issue report remains interesting, because SQLite exhibits inconsistent behaviors depending of the invalidated statements. But the real fix for "my" issue is to refactor my use of authorizers. On Thu, Aug 1, 2019 at 10:47 PM Gwendal Roué <gwendal.r...@gmail.com> wrote: > For the context, GRDB uses authorizers as a support for its database > observation features: > > - during the compilation of a read statements in order to know what part > of the database would be accessed by the statement. > - during the compilation of other statements in order to know what part of > the database would be modified, or which transaction/savepoint operation > would be executed, or if the database schema would change. > - during the execution of statements for the sole purpose of preventing > the truncate optimization when the library user has expressed the desire of > being notified of row deletions. > > Joined together, all those pieces of observation allow the library user to > say that it wants to track a "database region" (sets of tables, columns, > and rowids), and be notified of any transaction that has committed changes > to this region. This is insanely useful. With full support for raw SQL. > > I'm not sure this is what authorizers were designed for, but... I can't > live without them now :-) > > On Thu, Aug 1, 2019 at 10:26 PM Gwendal Roué <gwendal.r...@gmail.com> > wrote: > >> Yes, Richard, this fixes the problem! Tested with my local copy of SQLite >> 3.28.0. >> >> On Thu, Aug 1, 2019 at 9:23 PM Richard Hipp <d...@sqlite.org> wrote: >> >>> On 8/1/19, Gwendal Roué <gwendal.r...@gmail.com> wrote: >>> > >>> > 1. set authorizer >>> > 2. compile statement >>> > 3. reset authorizer >>> > 4. step >>> > 5. set authorizer (and do something else) >>> > 6. step -> SQLITE_ABORT_ROLLBACK >>> >>> Please test to see if changing the "0" to a "1" on the line of code >>> shown below fixes the problem, and report back. >>> >>> https://www.sqlite.org/src/artifact/0fac710388?ln=81 >>> -- >>> 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
