Wouldn’t your program already know what the values are as it passed them over the FFI initially? Why not hold onto that state?
On Mon, 11 Nov 2019 at 17:57, x <[email protected]> wrote: > Is http://www.sqlite.org/c3ref/expanded_sql.html no use to you? > > > > ________________________________ > From: sqlite-users <[email protected]> on > behalf of tab <[email protected]> > Sent: Monday, November 11, 2019 5:26:42 PM > To: [email protected] < > [email protected]> > Subject: [sqlite] [draft patch] interface for retrieving values of bound > parameters > > Hi all, > > It'd be handy to be able to retrieve params previously bound to a > statement in the C API. Per the advice on the SQLite copyright info page, > this is much more of a suggestion than a full patch, though it is > functional for binding and retrieving an sqlite_value* (but, for example, > there might be further implications not considered here in allowing the > contents of aVar to be used directly.) There wouldn't be much value in > maintaining a fork for something like this, so I wanted to put that out > here on the mailing list to see if it's something that might be considered > for mainline. > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
