On Fri, Sep 20, 2013 at 9:23 AM, Keith Medcalf <kmedc...@dessus.com> wrote:
> > Nice fix Richard, and it works as you have documented. > > With the added [cebd6fc551] to reset iCurrentTime when the statement is > reset, my testing indicates that if the p->iCurrentTime=0; added at line > 570 of vdbe.c by the original patch [daf6ba413c] (change fragment > [56e648f5ba9a9181]) is removed, then 'now' is stable for the statement > rather than just each step. > > That is, 'now' is stable from its first "access" in a statement until that > statement is reset. Unless you have found that it causes other issues (I > haven't found any yet) then removing the above mentioned clearing of > iCurrentTime during each step will result in SQLite's concept of 'now' > being consistent with that implemented in other SQL engines and in the > standard. > That's why I added the iCurrentTime clear to sqlite3_reset(), so that commenting out the iCurrentTime reset in sqlite3_step() would cause the behavior you describe. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
