On Sun, Apr 6, 2014 at 8:15 PM, Dominique Devienne <[email protected]> wrote: > [...]. I'd much prefer a cleaner Oracle-like TABLE() > operator transforming the result array of a table-function operating > on correlated values from a join as an intermediate result-set, i.e. > > select t.key, csv.COLUMN_VALUE from table t TABLE(scvsplit(t.csvfield)) csv
For those interested, here's an article along the same lines that better demonstrate what I mean by the above: http://technology.amis.nl/2013/06/26/oracle-database-12c-joining-and-outer-joining-with-collections/ The new Oracle 12c join syntax is basically just syntax sugar hiding the TABLE operator and its implicit COLUMN_VALUE column. Obviously SQLite does not have collection types, nor a TABLE operator, but it does have virtual tables, which are very similar to collection-returning functions in a way, and already "abused" by Max (I say that in a nice way) to the same effect. So the only piece that's missing is an official way to use vtables "on the fly", and pass in to its xFilter method the value from the left-correlated value for each joined left value, so the resulting cursor can "iterate" the right values. FWIW. --DD _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
