I was using it to get the rowid of a given cursor in a SQLite statement. Given a table schema like CREATE TABLE foo (A,B)
And an arbitrary select such as SELECT * FROM foo I was able to return the rowid as a hidden column for the statement. This included statements with multiple cursors (as a result of multiple joins). -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of D. Richard Hipp Sent: Saturday, April 17, 2010 11:08 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Question on the VdbeCursor structure changes On Apr 17, 2010, at 1:02 PM, Paul Shaffer wrote: > Due to changes in VdbeCursor structure, this code for 3.6.16 won't > compile > anymore: > > else if(pC->pseudoTable) > { > *prowid = pC->iKey; > } > Your application should not be messing with internal data structures of SQLite, all of which are subject to change without notice (as you have discovered.) Perhaps if you explain to us what you are trying to accomplish we will be better able to help you. > and for 3.6.23 would have to be replaced by something like this: > > else if(pC->pseudoTableReg>0) > { > //*prowid = ???? > } > > My problem is that after about an hour of reverse engineering I can't > figure out a way to get the row id with the new code. Any help > appreciated. > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
