Look at what that page says about "union all" (emphasis on *all*)
--SNIP--
"Note that the UNION ALL operator for compound queries does not use
transient indices by itself (though of course the right and left
subqueries of the UNION ALL might use transient indices depending on how
they are composed.)"
--/SNIP--
At least to my eyes, above says what i was expecting before realizing
what actually happens, that "union all" tries to not materialize its
results when possible.
What the truth is, concerning materialization, is that in SQLite "union
all" works exactly like plain "union". It always materializes its input.
lefteris.
On 29/10/12 16:37, Clemens Ladisch wrote:
Eleytherios Stamatogiannakis wrote:
Can a warning about "union all"'s behaviour of buffering everything in /var/tmp
be added in SQLite's documentation?
Like this? http://www.sqlite.org/tempfiles.html
Regards,
Clemens
_______________________________________________
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
