On Wed, Mar 8, 2017 at 3:47 AM, petern <peter.nichvolo...@gmail.com> wrote:
> Things have changed somewhat since I wrote those comments. After the > introduction of row values in 3.15 https://www.sqlite.org/rowvalue.html , > at least, now the sqlite ecosystem can cope with efficient vector valued > data for passing parameters into and out of the hypothetical eval() or > meta() vtab module. > How so? There are zero API functions taking or returning "row values", which is currently a pure SQL abstraction, and not a "physical" vector of values you can manipulate. You can create an eval() function now, via an eponymous vtable IMHO [1]. it just won't participate in the outer query plan, of course. --DD [1] https://www.sqlite.org/vtab.html#eponymous_virtual_tables _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
