Re: [sqlite] Correct use of sqlite3_vtab_nochange/sqlite3_value_nochange

2019-08-13 Thread Kevin Martin
> On 13 Aug 2019, at 14:08, Richard Hipp wrote: > > I think that is correct. > Great, thanks. > But it never occurred to me that somebody might do this on the PRIMARY > KEY. I don't see any reason why it wouldn't work, though. I have a c++ interface built on top of the virtual table api

Re: [sqlite] Correct use of sqlite3_vtab_nochange/sqlite3_value_nochange

2019-08-13 Thread Richard Hipp
On 8/10/19, Kevin Martin wrote: > Hi, > > I have a without rowid virtual table with an implementation of xColumn that > begins with > > if(sqlite3_vtab_nochange(ctx)) return SQLITE_OK; > > If I try to perform an update on this table that doesn't involve a primary > key change, then my

[sqlite] Correct use of sqlite3_vtab_nochange/sqlite3_value_nochange

2019-08-10 Thread Kevin Martin
Hi, I have a without rowid virtual table with an implementation of xColumn that begins with if(sqlite3_vtab_nochange(ctx)) return SQLITE_OK; If I try to perform an update on this table that doesn't involve a primary key change, then my understanding from the documentation is that xUpdate will